Triple
T38586283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cataclysm |
E932352
|
entity |
| Predicate | addsStartingZone |
P100142
|
FINISHED |
| Object | Gilneas |
—
|
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: Gilneas | Statement: [Cataclysm, addsStartingZone, Gilneas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsStartingZone Context triple: [Cataclysm, addsStartingZone, Gilneas]
-
A.
startingZoneFor
Indicates the zone or area where an entity initially begins, is placed, or starts its activity or process.
-
B.
hasStartingArea
Indicates that an entity is associated with, or begins from, a specific initial area or region.
-
C.
zoneAdded
chosen
Indicates that a new zone has been created and incorporated into an existing system, area, or configuration.
-
D.
laneStart
Indicates the point or position where a lane begins or first becomes active within a roadway or path.
-
E.
startingGuard
Indicates that an entity serves as the primary or first-choice guard in a lineup, formation, or configuration.
- 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.