Triple
T11476212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Dutch Football Association |
E272029
|
entity |
| Predicate | receivedRoyalStatus |
P44258
|
FINISHED |
| Object | 1895 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1895 | Statement: [Royal Dutch Football Association, receivedRoyalStatus, 1895]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedRoyalStatus Context triple: [Royal Dutch Football Association, receivedRoyalStatus, 1895]
-
A.
hasRoyalStatus
chosen
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
B.
royalAppointment
Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
-
C.
coronationStatus
Indicates the current stage or condition of an entity’s coronation process, such as whether it is pending, ongoing, or completed.
-
D.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
E.
nobleRankGrantedBy
Indicates that a particular noble rank or title was formally conferred upon someone by a specific granting authority or person.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294c8dc48190a515f83c99405a3b |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.