Triple
T3114361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 73 |
E65024
|
entity |
| Predicate | partiallyCompleted |
P45410
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Interstate 73, partiallyCompleted, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyCompleted Context triple: [Interstate 73, partiallyCompleted, true]
-
A.
partiallyRestored
Indicates that an entity has been brought back toward a previous or original state, but the restoration is incomplete or only partially achieved.
-
B.
partiallyPreserved
Indicates that the referenced entity or object is only incompletely intact, with some parts missing, damaged, or lost while others remain.
-
C.
reopenedPartially
Indicates that an entity that was previously closed or inactive has been opened again, but only to a limited or incomplete extent.
-
D.
partiallyDestroyed
Indicates that an entity has been damaged or ruined to a significant extent but not completely destroyed.
-
E.
partiallySuccessor
Indicates that one entity follows another in a sequence or process, but only to a limited or incomplete extent rather than as a full or direct successor.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada43dca688190ab041554220c5271 |
completed | March 8, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.