Triple
T23476770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZAPU |
E570283
|
entity |
| Predicate | unityAccordDate |
P6878
|
FINISHED |
| Object | 22 December 1987 |
—
|
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: 22 December 1987 | Statement: [ZAPU, unityAccordDate, 22 December 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unityAccordDate Context triple: [ZAPU, unityAccordDate, 22 December 1987]
-
A.
integratedDate
Indicates the date on which one entity was incorporated, combined, or brought into a larger system or whole.
-
B.
startDateConvention
Indicates the rule or method used to determine the effective start date of a period, contract, or calculation.
-
C.
accessionDate
Indicates the date on which an item, record, or entity was formally added to a collection, system, or repository.
-
D.
agreementSignedAt
Indicates the specific time and/or place at which an agreement was formally signed.
-
E.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74cf57081909d2b90a806d68c08 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:01 p.m.