Triple
T29329123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philae |
E743729
|
entity |
| Predicate | discoveryOfFinalLocationDate |
P3836
|
FINISHED |
| Object | 2016-09-02 |
—
|
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: 2016-09-02 | Statement: [Philae, discoveryOfFinalLocationDate, 2016-09-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryOfFinalLocationDate Context triple: [Philae, discoveryOfFinalLocationDate, 2016-09-02]
-
A.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
B.
remainsDiscoveredOn
Indicates that the physical remains of an entity were found or uncovered at a particular location or site.
-
C.
discoveryOfRemainsDate
Indicates the date on which the remains were discovered.
-
D.
locatedAtTimeOfDiscovery
Indicates the place where something was situated at the moment it was first discovered.
-
E.
discoveryDate
chosen
Indicates the date on which something was first discovered or identified.
- 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_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 1:28 p.m.