Triple
T26260543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beinn Mhor |
E656834
|
entity |
| Predicate | hasRelativeHeightCategory |
P161096
|
FINISHED |
| Object | major Marilyn |
—
|
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: major Marilyn | Statement: [Beinn Mhor, hasRelativeHeightCategory, major Marilyn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeHeightCategory Context triple: [Beinn Mhor, hasRelativeHeightCategory, major Marilyn]
-
A.
relativeHeightCategory
Indicates the comparative height relationship between entities, classifying one as taller, shorter, or similar in height relative to another.
-
B.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
C.
hasRelativeSize
Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
-
D.
heightRelation
chosen
Indicates a comparative relationship between entities based on their heights, such as one being taller, shorter, or the same height as another.
-
E.
hasSignificantHeight
Indicates that one entity’s height is notably large or substantial relative to a given standard or to other entities.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 26, 2026, 9:10 p.m.