Triple
T32893428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 91 |
E841399
|
entity |
| Predicate | formerConnects |
P19343
|
FINISHED |
| Object | Los Angeles area |
—
|
NE NERFINISHED |
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: Los Angeles area | Statement: [U.S. Route 91, formerConnects, Los Angeles area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerConnects Context triple: [U.S. Route 91, formerConnects, Los Angeles area]
-
A.
formerlyConnectedTo
chosen
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
-
B.
modernConnects
Indicates a contemporary or up-to-date form of connection or linkage established between two entities.
-
C.
formerNetwork
Indicates that an entity was previously part of, or affiliated with, a particular network but is no longer currently associated with it.
-
D.
formerNorthernConnection
Indicates that a prior relationship or linkage existed in the past between entities located in, associated with, or part of a northern region, but that connection no longer holds.
-
E.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
Created at: May 1, 2026, 1:18 a.m.