Triple
T14419947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberon Plateau |
E357555
|
entity |
| Predicate | surfaceAgeCharacteristic |
P50923
|
FINISHED |
| Object | ancient |
—
|
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: ancient | Statement: [Oberon Plateau, surfaceAgeCharacteristic, ancient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceAgeCharacteristic Context triple: [Oberon Plateau, surfaceAgeCharacteristic, ancient]
-
A.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
B.
surfaceDescription
Indicates that one entity provides a textual or qualitative description of the surface characteristics or appearance of another entity.
-
C.
ageModel
chosen
Indicates a relationship where one entity specifies or provides the age of another entity, typically in terms of a particular age value or age-related classification.
-
D.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
-
E.
surfaceQuality
Indicates the condition or characteristics of an entity’s outer surface, such as its smoothness, roughness, or finish.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de910eb354819089d5d5a46919eb49 |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.