Triple
T6932678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakistan Railways network |
E160473
|
entity |
| Predicate | dominantGauge |
P74353
|
FINISHED |
| Object | 5 ft 6 in broad gauge |
—
|
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: 5 ft 6 in broad gauge | Statement: [Pakistan Railways network, dominantGauge, 5 ft 6 in broad gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantGauge Context triple: [Pakistan Railways network, dominantGauge, 5 ft 6 in broad gauge]
-
A.
primaryGauge
Indicates that one gauge is designated as the main or principal measurement instrument among a set of gauges.
-
B.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
C.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
D.
dominatingFeature
Indicates that one feature stands out as the most prominent or influential characteristic in relation to others.
-
E.
dominantComposition
Indicates that one entity is the primary or prevailing component, material, or element that makes up or characterizes another entity.
- F. None of above. chosen
Provenance (4 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6e0c620f0819080e0ec49b36d4c30 |
completed | March 27, 2026, 7:55 p.m. |
Created at: March 27, 2026, 2:27 p.m.