Triple
T18747675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian broad gauge |
E458445
|
entity |
| Predicate | infrastructureElements |
P19374
|
FINISHED |
| Object | rails |
—
|
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: rails | Statement: [Indian broad gauge, infrastructureElements, rails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infrastructureElements Context triple: [Indian broad gauge, infrastructureElements, rails]
-
A.
isPartOfInfrastructure
chosen
Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
-
B.
identifiesInfrastructure
Indicates that one entity recognizes, designates, or specifies another entity as infrastructure within a given context.
-
C.
isPartOfInfrastructureType
Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
-
D.
infrastructureFocusArea
Indicates the specific aspect or domain of infrastructure that an entity, project, or activity is primarily concerned with or directed toward.
-
E.
physicalInfrastructure
Indicates that one entity serves as, or is part of, the tangible built environment or facilities that support the operation or existence of 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579e9903c81908180c46012bd0948 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.