Triple
T29571125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of the Crown of Romania |
E753312
|
entity |
| Predicate | monarchAsHead |
P136121
|
FINISHED |
| Object | King of Romania |
—
|
NE NERFINISHED |
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: King of Romania | Statement: [Order of the Crown of Romania, monarchAsHead, King of Romania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchAsHead Context triple: [Order of the Crown of Romania, monarchAsHead, King of Romania]
-
A.
monarchAsHeadOfOrder
chosen
Indicates that a monarch serves as the official head or leader of a particular order, such as an order of chivalry or honor.
-
B.
monarchIs
Indicates that one entity serves as the ruling monarch (such as king, queen, or equivalent sovereign) of another entity, typically a state or territory.
-
C.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
D.
monarch
Indicates that an entity serves as the sovereign ruler (such as a king, queen, or emperor) over a state or territory.
-
E.
monarchIsParentOf
Indicates that a monarch has a parent-child relationship with another individual, where the monarch is the parent.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 5:58 p.m.