Triple
T23836179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roncevaux Terra |
E590858
|
entity |
| Predicate | bodyTypeOfParent |
P2880
|
FINISHED |
| Object | satellite of Saturn |
—
|
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: satellite of Saturn | Statement: [Roncevaux Terra, bodyTypeOfParent, satellite of Saturn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyTypeOfParent Context triple: [Roncevaux Terra, bodyTypeOfParent, satellite of Saturn]
-
A.
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.
-
B.
parentType
Indicates that one entity serves as the direct parent or higher-level type from which another entity is derived or classified.
-
C.
typeOfBody
chosen
Indicates that one entity is the classification or kind of physical body that the other entity is.
-
D.
bodyNumber
Indicates the numerical position or identifier assigned to a body within a sequence or collection of bodies.
-
E.
bodyTypeDepicted
Indicates that one entity visually represents or portrays the physical body type of 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c882f9148190bb28fe7566ef1e70 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:07 p.m.