Triple
T16309974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of the House of Orange |
E396026
|
entity |
| Predicate | orderHeadTitle |
P4204
|
FINISHED |
| Object | Grand Master |
—
|
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: Grand Master | Statement: [Order of the House of Orange, orderHeadTitle, Grand Master]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderHeadTitle Context triple: [Order of the House of Orange, orderHeadTitle, Grand Master]
-
A.
orderName
Indicates the designated name or label assigned to a specific order in a transaction or ordering process.
-
B.
headOfOrder
chosen
Indicates that one entity holds the primary leadership or highest authority position within a particular order or organized group.
-
C.
orderType
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
D.
orderCommonName
Indicates that one entity is the commonly used (vernacular) name associated with a particular taxonomic order.
-
E.
orderFoundedBy
Indicates that a particular order or organization was established or created by a specific person or 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288d9557c81909203cd47aebf0f44 |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.