Triple
T32375638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CODESA |
E827270
|
entity |
| Predicate | CODESA IIDate |
P173988
|
FINISHED |
| Object | May 1992 |
—
|
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: May 1992 | Statement: [CODESA, CODESA IIDate, May 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CODESA IIDate Context triple: [CODESA, CODESA IIDate, May 1992]
-
A.
CODESA IDate
chosen
Indicates that there exists a specific date associated with the coding or encoding activity represented by the predicate.
-
B.
icoDate
Indicates the date on which an initial coin offering (ICO) occurs or is scheduled to occur.
-
C.
integratedDate
Indicates the date on which one entity was incorporated, combined, or brought into a larger system or whole.
-
D.
CBEDate
Indicates a relationship where a specific date is associated with the commencement or occurrence of a CB-related event or status.
-
E.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:50 a.m.