Triple
T33111989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arathorn II |
E847353
|
entity |
| Predicate | yearOfBecomingChieftain |
P194088
|
FINISHED |
| Object | T.A. 2930 |
—
|
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: T.A. 2930 | Statement: [Arathorn II, yearOfBecomingChieftain, T.A. 2930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfBecomingChieftain Context triple: [Arathorn II, yearOfBecomingChieftain, T.A. 2930]
-
A.
swornInAt
Indicates that an individual formally assumes an official role or office at a specific place or event through an oath or swearing-in ceremony.
-
B.
startTimeAsCaptain
Indicates the point in time when an entity first assumes the role or position of captain.
-
C.
ageAtFirstInvestiture
Indicates the age a person was when they first received an investiture, appointment, or formal conferral of office or authority.
-
D.
servedAsCaptainFrom
Indicates that an entity held the role of captain of another entity starting from a specified point in time.
-
E.
yearRaised
Indicates the specific year in which a particular amount of money or funding was raised.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
| PDg | Predicate description generation | batch_69fd5f2903a48190ac4b718bff99c6cf |
completed | May 8, 2026, 3:57 a.m. |
Created at: May 1, 2026, 1:27 a.m.