Triple
T38585202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patch 2.1 – Black Temple |
E932330
|
entity |
| Predicate | introducedZone |
P100142
|
FINISHED |
| Object | Black Temple |
—
|
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: Black Temple | Statement: [Patch 2.1 – Black Temple, introducedZone, Black Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedZone Context triple: [Patch 2.1 – Black Temple, introducedZone, Black Temple]
-
A.
introducedAsSingleZone
Indicates that something is presented or defined as a single, unified zone rather than being divided into multiple zones.
-
B.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
-
C.
zoneSystemIntroduced
Indicates that a particular zone-based system has been formally brought into use or implemented.
-
D.
zoneAdded
chosen
Indicates that a new zone has been created and incorporated into an existing system, area, or configuration.
-
E.
introducedSubdivision
Indicates that one entity created or formally established a new subdivision or sub-unit within another entity or structure.
- 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_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:32 p.m.