Triple
T3609464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 580 (Nevada) |
E76449
|
entity |
| Predicate | formsConcurrencyWith |
P2416
|
FINISHED |
| Object | U.S. Route 395 |
—
|
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: U.S. Route 395 | Statement: [Interstate 580 (Nevada), formsConcurrencyWith, U.S. Route 395]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsConcurrencyWith Context triple: [Interstate 580 (Nevada), formsConcurrencyWith, U.S. Route 395]
-
A.
requiresConcurrenceWith
Indicates that one action, decision, or condition must be agreed upon or approved by another specified party or entity before it can proceed or be valid.
-
B.
confluenceWith
chosen
Indicates that one entity joins or merges together with another, typically at a shared meeting point.
-
C.
heldConcurrentlyWith
Indicates that two or more events, roles, or states occurred or were in effect at the same time.
-
D.
concurrentModel
Indicates that two or more processes, activities, or states occur or are valid at the same time, potentially interacting or overlapping in execution.
-
E.
hasConcurrencyConstruct
Indicates that something includes or utilizes a construct or mechanism for executing multiple operations or tasks concurrently.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc22b824c8190a85b36185d4957bb |
completed | March 8, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.