Triple
T36345621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaman border crossing |
E895054
|
entity |
| Predicate | hasBeenClosedTemporarily |
P85990
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chaman border crossing, hasBeenClosedTemporarily, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenClosedTemporarily Context triple: [Chaman border crossing, hasBeenClosedTemporarily, yes]
-
A.
temporarilyClosedAfter
Indicates that one entity becomes temporarily closed or unavailable following the occurrence or completion of another entity or event.
-
B.
temporarilyClosedFrom
chosen
Indicates that an entity is not accessible or operating for a specific, limited time period starting from a given point.
-
C.
isTemporary
Indicates that the relationship, state, or condition holds only for a limited or non-permanent duration.
-
D.
permanentlyClosed
Indicates that an entity has ceased operations or availability and will not reopen or resume in the future.
-
E.
temporarilyRestored
Indicates that a previously unavailable or altered state, condition, or connection has been brought back to its former status for a limited or non-permanent period.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:09 p.m.