Triple
T35830478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guardian of Tirisfal |
E1035783
|
entity |
| Predicate | titleHolderLimit |
P200502
|
FINISHED |
| Object | one Guardian at a time |
—
|
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: one Guardian at a time | Statement: [Guardian of Tirisfal, titleHolderLimit, one Guardian at a time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderLimit Context triple: [Guardian of Tirisfal, titleHolderLimit, one Guardian at a time]
-
A.
titleHolderUnder
Indicates that one entity holds a title, position, or rank under the authority, jurisdiction, or hierarchy of another entity.
-
B.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
C.
titleHolderSatIn
Indicates that the title holder occupied a seat or position in a specified place or context.
-
D.
titleHolderDuring
Indicates that one entity holds a specific title or position during a defined time period in relation to another entity.
-
E.
titleHolderIsUsually
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
| PDg | Predicate description generation | batch_69ff90b5b98881909620033d78e4a9b8 |
completed | May 9, 2026, 7:53 p.m. |
Created at: May 3, 2026, 4:06 p.m.