Triple
T26396378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARM |
E663568
|
entity |
| Predicate | locatedInScotland |
P80099
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ARM, locatedInScotland, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInScotland Context triple: [ARM, locatedInScotland, true]
-
A.
builtInScotland
Indicates that something was constructed or created within the geographical boundaries of Scotland.
-
B.
locatedInBritishCountry
chosen
Indicates that one entity is geographically or administratively situated within a country that is part of the United Kingdom.
-
C.
hasCapitalCityOfScotland
Indicates the relationship in which an entity has, as its capital city, the city that serves as the capital of Scotland.
-
D.
EdinburghLocatedIn
Indicates that the entity Edinburgh is geographically or administratively situated within a specified larger region or jurisdiction.
-
E.
isLocatedInPartOfEngland
Indicates that one entity is geographically situated within a specific part or region 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 26, 2026, 11:29 p.m.