Triple
T5509100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dione |
E144515
|
entity |
| Predicate | possibleInternalStructure |
P22287
|
FINISHED |
| Object | rocky core |
—
|
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: rocky core | Statement: [Dione, possibleInternalStructure, rocky core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleInternalStructure Context triple: [Dione, possibleInternalStructure, rocky core]
-
A.
internalStructure
chosen
Indicates that one entity is a component, part, or substructure contained within the overall structure of another entity.
-
B.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
C.
integratedStructure
Indicates that multiple components are combined into a single, cohesive structure that functions as an integrated whole.
-
D.
containsStructureFrom
Indicates that one entity includes or incorporates a structural component originating from another entity.
-
E.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f4a80d88190bab0056c4c78be93 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.