Triple
T29329124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philae |
E743729
|
entity |
| Predicate | finalLocationIdentifiedBy |
P106636
|
FINISHED |
| Object | Rosetta OSIRIS camera |
—
|
NE NERFINISHED |
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: Rosetta OSIRIS camera | Statement: [Philae, finalLocationIdentifiedBy, Rosetta OSIRIS camera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalLocationIdentifiedBy Context triple: [Philae, finalLocationIdentifiedBy, Rosetta OSIRIS camera]
-
A.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
B.
lastLocation
Indicates the most recent known place or position where an entity was located.
-
C.
finalHomeOf
Indicates that a location is the last or ultimate home, residence, or resting place of an entity.
-
D.
positionConfirmedBy
chosen
Indicates that the validity or accuracy of a position (e.g., spatial, organizational, or conceptual) is verified or endorsed by a specified confirming entity.
-
E.
exactLocationKnown
Indicates that the precise geographic or spatial position of an entity is known and specified.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 28, 2026, 1:28 p.m.