Triple
T4747971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auckland volcanic field |
E105406
|
entity |
| Predicate | containsFeatureType |
P39038
|
FINISHED |
| Object | scoria cones |
—
|
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: scoria cones | Statement: [Auckland volcanic field, containsFeatureType, scoria cones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsFeatureType Context triple: [Auckland volcanic field, containsFeatureType, scoria cones]
-
A.
hasFeatureClass
chosen
Indicates that an entity is associated with, or categorized under, a particular feature class that characterizes its type or nature.
-
B.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
D.
isFeatureOf
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
E.
hasTypeOfSupport
Indicates that one entity provides or is associated with a particular kind or category of support in relation to another entity.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64c567288190a420e6825ee72822 |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.