Triple
T37377558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 440 (Tennessee) |
E928331
|
entity |
| Predicate | resurfacedWith |
P149389
|
FINISHED |
| Object | asphalt |
—
|
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: asphalt | Statement: [Interstate 440 (Tennessee), resurfacedWith, asphalt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resurfacedWith Context triple: [Interstate 440 (Tennessee), resurfacedWith, asphalt]
-
A.
replacedSurfaceType
chosen
Indicates that one surface type has been substituted or changed to another surface type.
-
B.
formerSurface
Indicates that one entity previously served as the surface or outer layer of another entity, but no longer does so.
-
C.
laterSurface
Indicates that one surface or layer occurs or appears at a later time than another surface or layer in a sequence or process.
-
D.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
E.
rebuiltUnder
Indicates that an entity was reconstructed or restored while being subject to the authority, control, or governance of another entity.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.