Triple
T10787931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earthrise |
E254495
|
entity |
| Predicate | takenOnBody |
P95482
|
FINISHED |
| Object | Moon vicinity |
—
|
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: Moon vicinity | Statement: [Earthrise, takenOnBody, Moon vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takenOnBody Context triple: [Earthrise, takenOnBody, Moon vicinity]
-
A.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
B.
operatedOnBody
Indicates that a medical or surgical procedure was performed on a particular body or body part.
-
C.
seatOnBody
Indicates that one entity functions as a seat or seating surface that is physically attached or integrated to a body or body-like structure.
-
D.
firstUsedOnBody
Indicates that something was initially applied, worn, or used directly on a body (or body part) at a specific time or in a specific context.
-
E.
usesBodyPart
Indicates that an entity performs an action or function by employing a specific body part as a means or tool.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d65fcc8190ab5573a861409c56 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:17 p.m.