Triple
T31800858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A9 road (Scotland) |
E811731
|
entity |
| Predicate | passesThroughCouncilArea |
P77740
|
FINISHED |
| Object | Stirling council area |
—
|
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: Stirling council area | Statement: [A9 road (Scotland), passesThroughCouncilArea, Stirling council area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passesThroughCouncilArea Context triple: [A9 road (Scotland), passesThroughCouncilArea, Stirling council area]
-
A.
passesThroughDistrict
Indicates that something (such as a route, boundary, or path) traverses or goes through a particular district.
-
B.
passesThroughCounty
Indicates that a route, path, or boundary traverses or goes through a specified county.
-
C.
passesThroughGovernorate
Indicates that something (such as a route, boundary, or flow) traverses or goes through a particular governorate.
-
D.
passesThroughAdministrativeRegion
chosen
Indicates that a route, path, or movement crosses into or through the territory of a specified administrative region.
-
E.
passesThroughArea
Indicates that an entity moves or extends through the spatial region defined by another entity or area.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 30, 2026, 11:41 p.m.