Triple
T29329113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philae |
E743729
|
entity |
| Predicate | actualFinalRestingSite |
P34068
|
FINISHED |
| Object | Abydos region on 67P |
—
|
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: Abydos region on 67P | Statement: [Philae, actualFinalRestingSite, Abydos region on 67P]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualFinalRestingSite Context triple: [Philae, actualFinalRestingSite, Abydos region on 67P]
-
A.
finalHomeOf
chosen
Indicates that a location is the last or ultimate home, residence, or resting place of an entity.
-
B.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
C.
actualImpactSite
Indicates the location where an impact actually occurred, as opposed to a predicted, intended, or nominal impact site.
-
D.
finalSiteSelection
Indicates the decision or confirmation that a particular site has been chosen as the final location from among candidate options.
-
E.
regionOfFinal
Indicates the geographic or administrative region in which something ultimately occurs, is finalized, or reaches its final state.
- 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_69f6689891608190a721be24599c4edd |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:28 p.m.