Triple
T3188103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albany, Scotland |
E66750
|
entity |
| Predicate | usedAsTermFor |
P2506
|
FINISHED |
| Object | northern part of Scotland |
—
|
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: northern part of Scotland | Statement: [Albany, Scotland, usedAsTermFor, northern part of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsTermFor Context triple: [Albany, Scotland, usedAsTermFor, northern part of Scotland]
-
A.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
B.
isUsedAs
chosen
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
C.
usedAsSuffixTo
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
-
D.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
notPreferredTermFor
Indicates that one term is a non-preferred or deprecated label that should be replaced by another, preferred term in a controlled vocabulary or terminology system.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6e279288190843837751e852c9e |
completed | March 8, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ad9e04290481909092ddfbe6fdaabc |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.