Triple
T7408848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odysseus impact basin |
E170947
|
entity |
| Predicate | hostBodyType |
P76600
|
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: [Odysseus impact basin, hostBodyType, satellite of Saturn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostBodyType Context triple: [Odysseus impact basin, hostBodyType, satellite of Saturn]
-
A.
housesBodyType
Indicates that one entity serves as a container, location, or structure that accommodates or encloses a particular type of body or physical form.
-
B.
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.
-
C.
establishesBodyType
Indicates that an entity defines or sets the physical or structural body type of another entity.
-
D.
hostsBody
Indicates that one entity serves as the physical container or location in which another entity resides or is situated.
-
E.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f29acf588190a7c4056bdc4f3ffc |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f15c36d48190bc75353d3f67555a |
completed | March 27, 2026, 9:06 p.m. |
Created at: March 27, 2026, 3:10 p.m.