Triple
T10068728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandelier Tree |
E213162
|
entity |
| Predicate | hasCones |
P91933
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chandelier Tree, hasCones, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCones Context triple: [Chandelier Tree, hasCones, yes]
-
A.
hasMultipleCones
Indicates that an entity is associated with more than one cone-shaped object or structure.
-
B.
hasCone
Indicates that one entity possesses, is equipped with, or is characterized by a cone or cone-shaped component.
-
C.
hasSatelliteCones
Indicates that an entity (typically a volcano) possesses one or more smaller subsidiary cones located on or around its main structure.
-
D.
isOneOfMainConesOf
Indicates that an entity is among the primary or most important cones associated with another entity.
-
E.
hasConeType
Indicates that an entity possesses or is associated with a specific type or category of cone.
- F. None of above. chosen
Provenance (4 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcff8d9c08190bc030f1dcc696310 |
completed | April 2, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:58 p.m.