Triple
T5755686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Rolls |
E126959
|
entity |
| Predicate | meetingWithPartnerDate |
P26202
|
FINISHED |
| Object | 1904-05-04 |
—
|
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: 1904-05-04 | Statement: [Charles Rolls, meetingWithPartnerDate, 1904-05-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingWithPartnerDate Context triple: [Charles Rolls, meetingWithPartnerDate, 1904-05-04]
-
A.
meetingDay
chosen
Indicates the specific day on which a meeting is scheduled or takes place between the related entities.
-
B.
engagementDate
Indicates the date on which two entities formally become engaged or committed to a relationship or agreement.
-
C.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
-
D.
meetsBetween
Indicates that one entity meets or encounters another at some point between two specified reference points or times.
-
E.
mayMeetAt
Indicates that two or more entities are permitted or able to have a meeting or encounter at a specified place or time.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02906848c8190bf7b0d62f57c27fa |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.