Triple
T5776300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catbells |
E127449
|
entity |
| Predicate | hasRidgeShape |
P26647
|
FINISHED |
| Object | north–south ridge |
—
|
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: north–south ridge | Statement: [Catbells, hasRidgeShape, north–south ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRidgeShape Context triple: [Catbells, hasRidgeShape, north–south ridge]
-
A.
hasRidges
Indicates that one entity possesses raised, linear or patterned ridges on its surface or structure in relation to another entity or context.
-
B.
isRidge
chosen
Indicates that something has the form or function of a ridge, typically being a long, narrow raised or elevated feature relative to its surroundings.
-
C.
ridgeType
Indicates the specific morphological or structural category that a ridge belongs to within a classification of ridge forms.
-
D.
hasIrregularShape
Indicates that an entity possesses a form or outline that deviates from a regular, standard, or symmetrical shape.
-
E.
hasRind
Indicates that an entity possesses a tough, outer protective layer or skin (a rind).
- 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_69c008361fa88190aefa4dc41b051e7f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021d0c6088190ba670ddcdbf5ca3e |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.