Triple
T17003154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cairnsmore of Carsphairn |
E412499
|
entity |
| Predicate | hasExpansiveViews |
P126122
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cairnsmore of Carsphairn, hasExpansiveViews, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpansiveViews Context triple: [Cairnsmore of Carsphairn, hasExpansiveViews, true]
-
A.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
B.
hasViewThrough
Indicates that one entity can be seen or visually perceived through another entity acting as an intermediate medium or opening.
-
C.
hasViewingAngles
Indicates that one entity possesses or is characterized by specific viewing angles relative to another entity or reference frame.
-
D.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
E.
expandableTo
Indicates that one entity can be extended, enlarged, or developed to become or accommodate another entity.
- F. None of above. chosen
Provenance (4 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d37f8ba88190b8d32a1d09b6e6fd |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e378e037c88190935d732e0f10d5d7 |
completed | April 18, 2026, 12:28 p.m. |
Created at: April 10, 2026, 5:32 a.m.