Triple
T179678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Norway |
E3655
|
entity |
| Predicate | currentHolderStart |
P7037
|
FINISHED |
| Object | 17 January 1991 |
—
|
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: 17 January 1991 | Statement: [King of Norway, currentHolderStart, 17 January 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentHolderStart Context triple: [King of Norway, currentHolderStart, 17 January 1991]
-
A.
lastHolder
Indicates that the subject is the most recent entity to have possessed, owned, or held the object.
-
B.
hasFirstHolder
Indicates that an entity is associated with the earliest or original holder (e.g., owner, position-bearer, or title-holder) of something.
-
C.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
-
D.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
E.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
- F. None of above. chosen
Provenance (4 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a25900709c8190a65e778936be5dd5 |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2566b53d481909c0ed40dd3719e8c |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2582b7f648190b0ef676b8bdc1c65 |
completed | Feb. 28, 2026, 2:51 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.