Triple
T38584845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Black Morass |
E932322
|
entity |
| Predicate | timekeeperNPC |
P141646
|
FINISHED |
| Object | Sa'at |
—
|
NE NERFINISHED |
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: Sa'at | Statement: [The Black Morass, timekeeperNPC, Sa'at]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timekeeperNPC Context triple: [The Black Morass, timekeeperNPC, Sa'at]
-
A.
officialTimekeeper
chosen
Indicates that one entity serves as the formally designated timekeeper or time-recording authority for another entity or event.
-
B.
timeLoopGuardian
Indicates a role in which an entity protects, maintains, or oversees the integrity and continuity of a recurring or looping timeline.
-
C.
timeSystem
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
-
D.
timeCycle
Indicates a recurring temporal pattern or interval in which an event, state, or process regularly repeats.
-
E.
timeBehind
Indicates that one entity occurs or is positioned later in time than another, lagging behind it on a temporal scale.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.