Triple
T20479445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vinalia Faculae |
E502411
|
entity |
| Predicate | foundOnBody |
P32348
|
FINISHED |
| Object | Ceres in the asteroid belt |
—
|
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: Ceres in the asteroid belt | Statement: [Vinalia Faculae, foundOnBody, Ceres in the asteroid belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundOnBody Context triple: [Vinalia Faculae, foundOnBody, Ceres in the asteroid belt]
-
A.
locatedOnBody
chosen
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
B.
discoveredOnBodyBy
Indicates that a body was discovered by a particular person or agent.
-
C.
takenOnBody
Indicates that an item or object is physically carried or worn on a person’s body.
-
D.
bodyFound
Indicates that the location or circumstance where a body was discovered has been identified or recorded.
-
E.
wearsOnBodyPart
Indicates that an entity places or has an item worn on a specific part of its body.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b55d7a881909dfe3ea0e74b742b |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.