Triple
T30213048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alberto Korda |
E768121
|
entity |
| Predicate | signatureWorkDate |
P171070
|
FINISHED |
| Object | 1960-03-05 |
—
|
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: 1960-03-05 | Statement: [Alberto Korda, signatureWorkDate, 1960-03-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureWorkDate Context triple: [Alberto Korda, signatureWorkDate, 1960-03-05]
-
A.
dateSigned
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
B.
signatureWork
Indicates that the work is a defining or most representative creation associated with an entity (such as a person, group, or organization).
-
C.
signaturesTargetDate
Indicates the date by which the required signatures are expected to be obtained or completed.
-
D.
agreementSignedAt
Indicates the specific time and/or place at which an agreement was formally signed.
-
E.
signatureWorkType
Indicates the specific category or type of work that serves as a defining or primary example associated with an entity.
- F. None of above. chosen
Provenance (4 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 7:33 p.m.