Triple
T28141535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fern Pass |
E714353
|
entity |
| Predicate | hasInfrastructurePlan |
P10988
|
FINISHED |
| Object | discussed tunnel project |
—
|
LITERAL FINISHED |
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: discussed tunnel project | Statement: [Fern Pass, hasInfrastructurePlan, discussed tunnel project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfrastructurePlan Context triple: [Fern Pass, hasInfrastructurePlan, discussed tunnel project]
-
A.
hasInfrastructurePolicy
Indicates that an entity has established rules, plans, or guidelines governing the development, management, or use of infrastructure.
-
B.
hasInfrastructureAbove
Indicates that one entity’s infrastructure is physically located above or over another entity.
-
C.
hasManagementPlan
Indicates that an entity is associated with a defined management plan specifying how it should be overseen, maintained, or administered.
-
D.
hasPlan
chosen
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
E.
hasGlobalInfrastructure
Indicates that an entity possesses infrastructure, facilities, or operational capabilities that are distributed across multiple countries or regions worldwide.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 27, 2026, 9:53 p.m.