Triple
T19907331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zone System |
E478452
|
entity |
| Predicate | Zone V description |
P137778
|
FINISHED |
| Object | middle gray |
—
|
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: middle gray | Statement: [Zone System, Zone V description, middle gray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Zone V description Context triple: [Zone System, Zone V description, middle gray]
-
A.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
B.
zoneType
Indicates the classification or category of a zone that specifies its type or functional designation.
-
C.
formerZone
Indicates that an entity was previously designated as a particular zone or area but no longer holds that status.
-
D.
zoneBased
Indicates that the relationship or action is determined or constrained by specific geographic or logical zones.
-
E.
undergroundZone
Indicates that something is located in, associated with, or occurring within an area beneath the ground surface.
- F. None of above. chosen
Provenance (4 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6598cc5108190bca2a47c9f8ef70f |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:52 p.m.