Triple
T20479118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverness Corona |
E502402
|
entity |
| Predicate | surfaceStructure |
P127055
|
FINISHED |
| Object | ridges |
—
|
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: ridges | Statement: [Inverness Corona, surfaceStructure, ridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceStructure Context triple: [Inverness Corona, surfaceStructure, ridges]
-
A.
grammaticalStructure
Indicates the way linguistic elements are organized and related within a sentence or phrase according to grammatical rules.
-
B.
structureOnSurface
chosen
Indicates that one entity is a structure physically situated on the surface of another entity.
-
C.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
-
D.
structuralExpression
Indicates that one entity represents the structural or formal expression of another, such as a configuration, layout, or organized form that embodies its structure.
-
E.
textualStructure
Indicates how parts of a text are organized and related to each other within its overall structure.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b54c8188190a71e35fab8d194a6 |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.