Triple
T29860714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udny Station |
E758305
|
entity |
| Predicate | historicallyServedArea |
P82
|
FINISHED |
| Object | Formartine district |
—
|
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: Formartine district | Statement: [Udny Station, historicallyServedArea, Formartine district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyServedArea Context triple: [Udny Station, historicallyServedArea, Formartine district]
-
A.
historicallyServedBy
Indicates that an entity was provided with services or support by another entity during a past period of time.
-
B.
areaServed
chosen
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
C.
strategicAreaServed
Indicates that an entity provides services or exerts influence within a particular area considered strategically important.
-
D.
historicallyBasedIn
Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
-
E.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: April 29, 2026, 5:49 p.m.