Triple
T7852681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haakon V of Norway |
E182093
|
entity |
| Predicate | nobleRankBeforeKingship |
P53396
|
FINISHED |
| Object | duke |
—
|
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: duke | Statement: [Haakon V of Norway, nobleRankBeforeKingship, duke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleRankBeforeKingship Context triple: [Haakon V of Norway, nobleRankBeforeKingship, duke]
-
A.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
B.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
C.
rankBeforeKingship
Indicates that one entity held a higher or earlier rank or status than another entity prior to that other entity attaining kingship.
-
D.
nobleRankGrantedBy
Indicates that a particular noble rank or title was formally conferred upon someone by a specific granting authority or person.
-
E.
nobleRankType
chosen
Indicates the specific category or level of nobility associated with an entity within a hierarchical noble rank 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_69ca82869ee08190b8f9040dbc2c0467 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb18ec48548190960bd564a60effa8 |
completed | March 31, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:51 p.m.