Triple
T2726423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosetta mission |
E60203
|
entity |
| Predicate | rendezvousDate |
P26202
|
FINISHED |
| Object | 2014-08-06 |
—
|
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: 2014-08-06 | Statement: [Rosetta mission, rendezvousDate, 2014-08-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rendezvousDate Context triple: [Rosetta mission, rendezvousDate, 2014-08-06]
-
A.
meetingDay
chosen
Indicates the specific day on which a meeting is scheduled or takes place between the related entities.
-
B.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
-
C.
engagementDate
Indicates the date on which two entities formally become engaged or committed to a relationship or agreement.
-
D.
meetsVia
Indicates that two entities come into contact or interact with each other through a specified intermediary medium, channel, or mechanism.
-
E.
meetsBetween
Indicates that one entity meets or encounters another at some point between two specified reference points or times.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdace9f308190964a064859612cd6 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.