Triple
T34982273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federation–Cardassian Treaty |
E1008846
|
entity |
| Predicate | establishedZone |
P6793
|
FINISHED |
| Object | Federation–Cardassian Demilitarized 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: Federation–Cardassian Demilitarized Zone | Statement: [Federation–Cardassian Treaty, establishedZone, Federation–Cardassian Demilitarized Zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedZone Context triple: [Federation–Cardassian Treaty, establishedZone, Federation–Cardassian Demilitarized Zone]
-
A.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
-
B.
zoneStatus
Indicates the current operational or condition state assigned to a specific zone within a system or environment.
-
C.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
D.
zoneType
Indicates the classification or category of a zone that specifies its type or functional designation.
-
E.
hasZone
chosen
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:01 p.m.