Triple
T28071177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mull of Kintyre |
E709403
|
entity |
| Predicate | aSideOf |
P34740
|
FINISHED |
| Object | Mull of Kintyre / Girls’ School |
—
|
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: Mull of Kintyre / Girls’ School | Statement: [Mull of Kintyre, aSideOf, Mull of Kintyre / Girls’ School]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aSideOf Context triple: [Mull of Kintyre, aSideOf, Mull of Kintyre / Girls’ School]
-
A.
A-sideOf
chosen
Indicates that one entity is located on or corresponds to the A-side (first or primary side) of another entity, typically in a two-sided context.
-
B.
hasASideOf
Indicates that one entity possesses or includes a particular side or face as part of its structure or boundary.
-
C.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
-
D.
A-sideWith
Indicates that one entity is aligned or positioned on the same side as another entity.
-
E.
singleSideOf
Indicates that one entity constitutes a single side or face of another entity, typically within a larger multi-sided structure or object.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6403ca9a081908446eafd52a0c7b3 |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f637120c008190b2b5adf46f022e48 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:46 p.m.