Triple
T29329068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rubber duck comet |
E743728
|
entity |
| Predicate | PhilaeFinalRestingSiteName |
P53640
|
FINISHED |
| Object | Abydos |
—
|
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 | Statement: [rubber duck comet, PhilaeFinalRestingSiteName, Abydos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PhilaeFinalRestingSiteName Context triple: [rubber duck comet, PhilaeFinalRestingSiteName, Abydos]
-
A.
newLocationOfPhilae
chosen
Indicates the relationship where a specified place or position is the new, subsequent location of Philae after it has moved or been relocated.
-
B.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
-
C.
firstLandingSite
Indicates the location where an entity initially arrives, lands, or touches down before any subsequent movements or landings.
-
D.
plannedLandingSiteType
Indicates the type or category of location designated as the intended landing site.
-
E.
wasLandingSiteDuring
Indicates that a location served as the landing site for a particular event, mission, or vehicle during a specified time or context.
- 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_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 1:28 p.m.