Triple
T28623990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PA 43 |
E724465
|
entity |
| Predicate | partOfLongTermPlan |
P29774
|
FINISHED |
| Object | Mon–Fayette Expressway system |
—
|
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: Mon–Fayette Expressway system | Statement: [PA 43, partOfLongTermPlan, Mon–Fayette Expressway system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLongTermPlan Context triple: [PA 43, partOfLongTermPlan, Mon–Fayette Expressway system]
-
A.
partOfPlan
chosen
Indicates that one entity is included as a component or step within a broader plan or strategy.
-
B.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
C.
planningInvolves
Indicates that a planning process includes or takes into account a particular entity, factor, or activity as part of its considerations or steps.
-
D.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
E.
majorPlan
Indicates that an entity serves as a primary or central plan guiding major actions, decisions, or developments related to another entity.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 28, 2026, 4:35 a.m.