Triple
T29329112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philae |
E743729
|
entity |
| Predicate | designedLandingSite |
P185878
|
FINISHED |
| Object | Agilkia 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: Agilkia region on 67P | Statement: [Philae, designedLandingSite, Agilkia region on 67P]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedLandingSite Context triple: [Philae, designedLandingSite, Agilkia region on 67P]
-
A.
plannedLandingSiteType
Indicates the type or category of location designated as the intended landing site.
-
B.
sampleLandingSite
Indicates that a location is designated or used as the landing site for a particular sample.
-
C.
wasIntendedLandingSiteFor
chosen
Indicates that a particular location was designated or planned to be the landing site for a specific mission, vehicle, or object.
-
D.
hasMainLandingSite
Indicates that an entity has a primary or principal location where it arrives, lands, or makes contact.
-
E.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
- 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_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 28, 2026, 1:28 p.m.