Triple
T8470936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zone Information Protocol |
E200277
|
entity |
| Predicate | zoneNameEncoding |
P83494
|
FINISHED |
| Object | up to 32 characters |
—
|
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: up to 32 characters | Statement: [Zone Information Protocol, zoneNameEncoding, up to 32 characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneNameEncoding Context triple: [Zone Information Protocol, zoneNameEncoding, up to 32 characters]
-
A.
exampleZoneName
Indicates that an entity is associated with a zone identified by a specific example or placeholder name.
-
B.
zoneCode
Indicates that an entity is associated with, or assigned to, a specific geographic or administrative zone identified by a code.
-
C.
zoneType
Indicates the classification or category of a zone that specifies its type or functional designation.
-
D.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
E.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f234c481909534de6fd702f4cf |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:11 p.m.