Triple
T5238708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African Republic |
E118286
|
entity |
| Predicate | dateEventEnd |
P140
|
FINISHED |
| Object | 31 May 1902 |
—
|
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: 31 May 1902 | Statement: [South African Republic, dateEventEnd, 31 May 1902]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateEventEnd Context triple: [South African Republic, dateEventEnd, 31 May 1902]
-
A.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
B.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
C.
endDateOfEntries
Indicates the date on which the referenced entries conclude or are no longer valid.
-
D.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
E.
eventStartDateOrganized
Indicates the date on which an event is formally scheduled or organized to begin.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b290b88819095bc99c234260d25 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.