Triple
T34877381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solutions for Congested Corridors Program |
E1005914
|
entity |
| Predicate | focusesOn |
P31
|
FINISHED |
| Object | corridors with high travel demand |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: corridors with high travel demand | Statement: [Solutions for Congested Corridors Program, focusesOn, corridors with high travel demand]
Provenance (2 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7819d85a88190be0aa14ecdfd77c7 |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 3, 2026, 4 p.m.