Triple
T4437023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Officer of the Order of Orange-Nassau |
E95675
|
entity |
| Predicate | isRankIn |
P47925
|
FINISHED |
| Object | Dutch honours system |
—
|
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: Dutch honours system | Statement: [Grand Officer of the Order of Orange-Nassau, isRankIn, Dutch honours system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRankIn Context triple: [Grand Officer of the Order of Orange-Nassau, isRankIn, Dutch honours system]
-
A.
isRank
chosen
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
-
B.
isRankedAbove
Indicates that one entity holds a higher position or status in an ordered ranking than another entity.
-
C.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
D.
isEntryLevelRankFor
Indicates that a rank represents the lowest or starting level within a particular role, position, or hierarchy.
-
E.
hasLegalRank
Indicates that an entity holds a specific legal status, classification, or rank within a formal legal or regulatory system.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3558b1d4481909060ede5e0ded4bc |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:31 p.m.