Triple
T30293208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 99 |
E770438
|
entity |
| Predicate | concurrencyWith |
P169053
|
FINISHED |
| Object | U.S. Route 220 |
—
|
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 220 | Statement: [Interstate 99, concurrencyWith, U.S. Route 220]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concurrencyWith Context triple: [Interstate 99, concurrencyWith, U.S. Route 220]
-
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.
heldConcurrentlyWith
Indicates that two or more events, roles, or states occurred or were in effect at the same time.
-
C.
hasConcurrency
Indicates that two or more processes, tasks, or operations can occur or be executed simultaneously or with overlapping time intervals.
-
D.
isMostlyConcurrentWith
Indicates that two events or intervals overlap in time for the majority of their durations, though not necessarily starting or ending together.
-
E.
partlyConcurrentWith
Indicates that two events or intervals overlap in time for some, but not all, of their durations.
- F. None of above. chosen
Provenance (4 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6813533788190a30e47f0ba6afb74 |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 29, 2026, 7:47 p.m.