Triple
T26850003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Am Bràigh Riabhach |
E676031
|
entity |
| Predicate | rankingByHeightInScotland |
P74816
|
FINISHED |
| Object | third-highest |
—
|
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: third-highest | Statement: [Am Bràigh Riabhach, rankingByHeightInScotland, third-highest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingByHeightInScotland Context triple: [Am Bràigh Riabhach, rankingByHeightInScotland, third-highest]
-
A.
rankingInScotlandByHeight
chosen
Indicates the position of something in an ordered list of tallest entities specifically within Scotland.
-
B.
rankingInUnitedKingdomByHeight
Indicates the position of an entity in an ordered list based on its height within the United Kingdom.
-
C.
rankInScotlandByArea
Indicates the numerical position of an entity in an ordered list of areas specifically within Scotland, based on its size.
-
D.
formerRankInUKByHeight
Indicates that an entity previously held a specific rank in the United Kingdom when entities are ordered by height.
-
E.
rankingInEnglandByHeight
Indicates the relative position of an entity in an ordered list based on its height specifically within the context of England.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 5:15 a.m.