Triple
T21950733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Trough |
E542060
|
entity |
| Predicate | hasTypeOfOrigin |
P109994
|
FINISHED |
| Object | volcano-tectonic origin |
—
|
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: volcano-tectonic origin | Statement: [Emperor Trough, hasTypeOfOrigin, volcano-tectonic origin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfOrigin Context triple: [Emperor Trough, hasTypeOfOrigin, volcano-tectonic origin]
-
A.
hasNameOriginType
Indicates that there is a specific type or category describing the origin of an entity’s name.
-
B.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
-
D.
hasSettlementTypeOrigin
Indicates that an entity’s settlement type is derived from, or originates in, a specified source or origin.
-
E.
hasTypeOfSource
chosen
Indicates that one entity is classified as a particular kind or category of source 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243bb9c88190a3774b9fa2af9871 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:58 p.m.