Triple
T36939124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas State Highway 99 |
E913701
|
entity |
| Predicate | isPartiallyComplete |
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: [Texas State Highway 99, isPartiallyComplete, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartiallyComplete Context triple: [Texas State Highway 99, isPartiallyComplete, true]
-
A.
partiallyCompleted
chosen
Indicates that an action, process, or task has been started and progressed to some extent, but has not yet been fully completed.
-
B.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
C.
hasPartialResults
Indicates that an action, process, or query has produced some intermediate or incomplete results, but not the final or full outcome.
-
D.
hasPartialResultsIn
Indicates that an activity, process, or operation has produced intermediate or incomplete results within a given context or container.
-
E.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
Created at: May 3, 2026, 4:13 p.m.