Triple
T38061303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Arreat |
E950345
|
entity |
| Predicate | guardians |
P28704
|
FINISHED |
| Object | The Ancients on Arreat Summit |
—
|
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: The Ancients on Arreat Summit | Statement: [Mount Arreat, guardians, The Ancients on Arreat Summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardians Context triple: [Mount Arreat, guardians, The Ancients on Arreat Summit]
-
A.
guardian
chosen
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
B.
guardianInPlot
Indicates that one entity serves as a guardian or protector of another entity within the context of a specific plot or storyline.
-
C.
guardianDescription
Indicates that one entity serves as a protector or caretaker responsible for the welfare or oversight of another entity.
-
D.
guardianSpecies
Indicates a relationship where one species serves as a protector or guardian for another species.
-
E.
guard
Indicates that one entity protects, watches over, or defends another entity or resource from harm, intrusion, or unauthorized access.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.