Triple
T25685758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Highways Act, 1956 |
E644062
|
entity |
| Predicate | typeOfInfrastructureLaw |
P112493
|
FINISHED |
| Object | transport law |
—
|
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: transport law | Statement: [National Highways Act, 1956, typeOfInfrastructureLaw, transport law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfInfrastructureLaw Context triple: [National Highways Act, 1956, typeOfInfrastructureLaw, transport law]
-
A.
isPartOfInfrastructureType
Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
-
B.
typeOfLegislation
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
-
C.
isPartOfInfrastructure
Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
-
D.
typeOfTransportInfrastructure
Indicates the specific category or kind of transport infrastructure associated with or used in a given context.
-
E.
infrastructureFocusArea
chosen
Indicates the specific aspect or domain of infrastructure that an entity, project, or activity is primarily concerned with or directed toward.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 21, 2026, 8:08 p.m.