Triple
T25343625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Bridge of Irun–Hendaye |
E635481
|
entity |
| Predicate | gaugeSeparationPoint |
P64360
|
FINISHED |
| Object | Iberian gauge |
—
|
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: Iberian gauge | Statement: [International Bridge of Irun–Hendaye, gaugeSeparationPoint, Iberian gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaugeSeparationPoint Context triple: [International Bridge of Irun–Hendaye, gaugeSeparationPoint, Iberian gauge]
-
A.
gaugeGroup
Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
-
B.
gaugeType
Indicates the specific kind or category of gauge associated with an entity or measurement.
-
C.
gaugeRelationship
Indicates a relationship where one entity measures, assesses, or evaluates the state, quality, or degree of another entity.
-
D.
gaugeValue
Indicates the measured or current reading associated with a particular gauge or measurement instrument.
-
E.
separatesPointsOn
chosen
Indicates that one entity divides or partitions a set or space such that distinct points lie on different sides or regions relative to it.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:32 p.m.