Triple
T32271452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NC 540 |
E824423
|
entity |
| Predicate | isIncludedInPlan |
P98771
|
FINISHED |
| Object | Raleigh Outer Loop |
—
|
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: Raleigh Outer Loop | Statement: [NC 540, isIncludedInPlan, Raleigh Outer Loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIncludedInPlan Context triple: [NC 540, isIncludedInPlan, Raleigh Outer Loop]
-
A.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
B.
hasBasePlan
Indicates that an entity is associated with or derived from a specified foundational or default plan.
-
C.
initiallySupportsPlan
Indicates that an entity expresses support for a plan at the beginning of a process, period, or scenario.
-
D.
hasRelatedPlan
chosen
Indicates that one entity is associated with another entity through a plan that is relevant or connected to it.
-
E.
hasTypicalPlan
Indicates that there is a standard or commonly followed plan, procedure, or course of action typically associated with the given entity or situation.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc89010c8190982399d265f171ac |
completed | May 3, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:42 a.m.