Triple
T28841174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 493 |
E728317
|
entity |
| Predicate | existsInMaps |
P138987
|
FINISHED |
| Object | only as theoretical or list entry |
—
|
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: only as theoretical or list entry | Statement: [Interstate 493, existsInMaps, only as theoretical or list entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existsInMaps Context triple: [Interstate 493, existsInMaps, only as theoretical or list entry]
-
A.
existsFrom
Indicates that an entity comes into existence or begins to be valid starting from a specified point in time or condition.
-
B.
hasMaps
chosen
Indicates that one entity possesses, includes, or provides access to one or more maps associated with another entity.
-
C.
existsAs
Indicates that one entity has the same identity or manifestation as another, effectively asserting they are the same existing thing or state.
-
D.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
E.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:40 a.m.