Triple
T4090043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embassy of the United States in Havana |
E87683
|
entity |
| Predicate | reopeningFlagRaisingCeremonyDate |
P2731
|
FINISHED |
| Object | 2015-08-14 |
—
|
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: 2015-08-14 | Statement: [Embassy of the United States in Havana, reopeningFlagRaisingCeremonyDate, 2015-08-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopeningFlagRaisingCeremonyDate Context triple: [Embassy of the United States in Havana, reopeningFlagRaisingCeremonyDate, 2015-08-14]
-
A.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
B.
ceremonyHeldOn
chosen
Indicates that a specific ceremony took place on a particular date or day.
-
C.
relocationOpeningDate
Indicates the date on which a relocation (such as a move or transfer to a new place) is officially opened or becomes effective.
-
D.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
E.
rededicationDate
Indicates the date on which something is formally dedicated again, typically after restoration, change, or renewal.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcab0a1c8190a1b0ca48ebc95b31 |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.