Triple
T2805727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longshanks |
E54048
|
entity |
| Predicate | reignedAs |
P10353
|
FINISHED |
| Object | King of England |
—
|
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: King of England | Statement: [Longshanks, reignedAs, King of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignedAs Context triple: [Longshanks, reignedAs, King of England]
-
A.
reignAs
chosen
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
B.
regentOf
Indicates a relationship where one entity serves as the ruling authority or caretaker governing on behalf of another entity, typically during the latter’s minority, absence, or incapacity.
-
C.
wasCrowned
Indicates that an entity formally received a crown or royal title in a ceremonial act of investiture.
-
D.
electedMonarchOf
Indicates that one entity has been chosen through an election process to serve as the monarch (sovereign ruler) of another entity, typically a state or polity.
-
E.
reignDuration
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.