Triple
T26560888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puy de Pariou |
E666236
|
entity |
| Predicate | hasInnerFeature |
P6655
|
FINISHED |
| Object | steep inner crater walls |
—
|
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: steep inner crater walls | Statement: [Puy de Pariou, hasInnerFeature, steep inner crater walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInnerFeature Context triple: [Puy de Pariou, hasInnerFeature, steep inner crater walls]
-
A.
hasInternal
Indicates that one entity contains another entity within its internal structure or boundaries.
-
B.
hasInteriorFeature
chosen
Indicates that an entity contains or includes a specific feature within its interior space.
-
C.
hasIntermediateFeatures
Indicates that an entity possesses features or characteristics that are between two defined levels, states, or categories in a given context.
-
D.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
E.
hasUnitFeature
Indicates that something possesses a specific unit-related characteristic or attribute, such as a measurable feature expressed in defined units.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 27, 2026, 1:52 a.m.