Triple
T23725064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brig o’ Doon |
E586250
|
entity |
| Predicate | hasArchShape |
P153718
|
FINISHED |
| Object | highly cambered |
—
|
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: highly cambered | Statement: [Brig o’ Doon, hasArchShape, highly cambered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchShape Context triple: [Brig o’ Doon, hasArchShape, highly cambered]
-
A.
hasArchType
Indicates that one entity possesses or is characterized by a particular architectural type or style.
-
B.
hasSideArch
Indicates that one entity possesses or features a secondary or lateral arch structure in relation to another entity.
-
C.
hasArchetype
Indicates that one entity serves as the original model, pattern, or prototype upon which another entity is based or conceptually derived.
-
D.
hasHemShape
Indicates that an item possesses a specific form or contour of its hem or lower edge.
-
E.
hasNumberOfArches
Indicates the relationship specifying how many arches are present in or associated with a given 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b914adc08190b339c7f83f1536d7 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 7:08 p.m.