Triple
T10117978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian order of precedence |
E223210
|
entity |
| Predicate | includesRankFor |
P36072
|
FINISHED |
| Object | members of the Belgian Royal Family |
—
|
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: members of the Belgian Royal Family | Statement: [Belgian order of precedence, includesRankFor, members of the Belgian Royal Family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRankFor Context triple: [Belgian order of precedence, includesRankFor, members of the Belgian Royal Family]
-
A.
containsRank
Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
-
B.
rankStructureIncludes
chosen
Indicates that a given rank structure contains or encompasses a specified rank or set of ranks within its hierarchy.
-
C.
usesRank
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
D.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
-
E.
isRank
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd26317948190901197adbac01ed3 |
completed | April 2, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.