Triple
T11865453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 19/41 in Jonesboro |
E282268
|
entity |
| Predicate | hasConcurrency |
P101957
|
FINISHED |
| Object | U.S. Route 19 |
—
|
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 19 | Statement: [U.S. Route 19/41 in Jonesboro, hasConcurrency, U.S. Route 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConcurrency Context triple: [U.S. Route 19/41 in Jonesboro, hasConcurrency, U.S. Route 19]
-
A.
hasConcurrencyConstruct
Indicates that something includes or utilizes a construct or mechanism for executing multiple operations or tasks concurrently.
-
B.
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.
-
C.
isMostlyConcurrentWith
Indicates that two events or intervals overlap in time for the majority of their durations, though not necessarily starting or ending together.
-
D.
heldConcurrentlyWith
Indicates that two or more events, roles, or states occurred or were in effect at the same time.
-
E.
hasParallelIn
Indicates that one entity has a corresponding or analogous counterpart in another context, system, or domain.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73883508190a78b5f4ba4a220df |
completed | April 10, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69d8a2589f0c8190ad82ff11acabae93 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.