Triple
T28895684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chemical Plant Zone |
E732827
|
entity |
| Predicate | precedesZone |
P114670
|
FINISHED |
| Object | Aquatic Ruin Zone |
—
|
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: Aquatic Ruin Zone | Statement: [Chemical Plant Zone, precedesZone, Aquatic Ruin Zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesZone Context triple: [Chemical Plant Zone, precedesZone, Aquatic Ruin Zone]
-
A.
precedesDisc
Indicates that one discourse segment or unit occurs before another in the sequence of discourse.
-
B.
predecessorArea
chosen
Indicates that one area previously existed or was defined before another area in a sequence or versioning of areas.
-
C.
precedesInUniverse
Indicates that one event or entity occurs earlier than another within the timeline or causal order of a given fictional or conceptual universe.
-
D.
precedesLetter
Indicates that one letter comes immediately before another letter in a specified ordering, such as the alphabet or a given sequence.
-
E.
precedesInAscent
Indicates that one entity occurs or appears earlier than another in an ordered upward or ascending sequence.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 7:58 a.m.