Triple
T29934878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosetta |
E760330
|
entity |
| Predicate | rendezvousDateWith67P |
P84583
|
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, rendezvousDateWith67P, 2014-08-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rendezvousDateWith67P Context triple: [Rosetta, rendezvousDateWith67P, 2014-08-06]
-
A.
rendezvousWith
Indicates that two or more entities meet or come together at an agreed place and time, often for a specific purpose.
-
B.
rendezvousType
Indicates the specific kind or category of meeting or rendezvous that occurs between entities.
-
C.
rendezvousTarget
chosen
Indicates that one entity is designated as the meeting or rendezvous point for another entity.
-
D.
rendezvousSystem
Indicates a system or mechanism that coordinates and manages the meeting or docking of two or more entities at a specified place and time.
-
E.
rendezvousProfile
Indicates a relationship where entities coordinate to meet at a specific place and time, often under predefined conditions or plans.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677d413c081908203059402081897 |
completed | May 2, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:20 p.m.