Triple
T26912220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airdrie and Shotts |
E677419
|
entity |
| Predicate | coversCommunity |
P8617
|
FINISHED |
| Object | Calderbank |
—
|
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: Calderbank | Statement: [Airdrie and Shotts, coversCommunity, Calderbank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversCommunity Context triple: [Airdrie and Shotts, coversCommunity, Calderbank]
-
A.
includesCommunity
chosen
Indicates that one entity encompasses, contains, or has within it a particular community as part of its scope or composition.
-
B.
community
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
C.
communityAspect
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
D.
collaboratingCommunity
Indicates that two or more entities are actively working together toward shared goals or projects as part of a community relationship.
-
E.
focusesOnCommunity
Indicates that the subject prioritizes and directs attention or effort toward the well-being, needs, or development of a community.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 6:02 a.m.