Triple
T17909031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamondhead |
E447773
|
entity |
| Predicate | hasBodyComposition |
P129263
|
FINISHED |
| Object | Organic crystal |
—
|
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: Organic crystal | Statement: [Diamondhead, hasBodyComposition, Organic crystal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyComposition Context triple: [Diamondhead, hasBodyComposition, Organic crystal]
-
A.
managementBodyType
Indicates the type or category of governing or management body responsible for overseeing an entity.
-
B.
hasGivingBodyType
Indicates that one entity serves as the physical or organizational source that gives or grants something to another entity.
-
C.
parentBodyType
Indicates that one entity has a body type that serves as the parent or base classification from which another entity's body type is derived or organized.
-
D.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
-
E.
bodyThickness
Indicates the measured or relative thickness of an entity’s body in the context of a comparison or description.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49e9e4c9881908bfc3a83809d6b85 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
| PDg | Predicate description generation | batch_69e3db77df0c819084548168c62b398c |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:19 a.m.