Triple
T33612662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 30 |
E861030
|
entity |
| Predicate | isConcurrentWith |
P90003
|
FINISHED |
| Object | U.S. Route 98 |
—
|
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 98 | Statement: [SR 30, isConcurrentWith, U.S. Route 98]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConcurrentWith Context triple: [SR 30, isConcurrentWith, U.S. Route 98]
-
A.
isMostlyConcurrentWith
Indicates that two events or intervals overlap in time for the majority of their durations, though not necessarily starting or ending together.
-
B.
hasConcurrenceFrom
Indicates that an action, decision, or proposal is supported or agreed upon by another party or authority.
-
C.
partlyConcurrentWith
Indicates that two events or intervals overlap in time for some, but not all, of their durations.
-
D.
isSignedConcurrentWith
Indicates that two or more signing events occur during overlapping time periods, such that they are in effect or executed concurrently.
-
E.
isConcurrentWithOtherRoutes
chosen
Indicates that one route occurs or operates at the same time as one or more other routes.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1:41 a.m.