Triple
T9576076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innoventions |
E231048
|
entity |
| Predicate | closingDateDetail |
P82025
|
FINISHED |
| Object | April 30, 2015 |
—
|
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: April 30, 2015 | Statement: [Innoventions, closingDateDetail, April 30, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closingDateDetail Context triple: [Innoventions, closingDateDetail, April 30, 2015]
-
A.
closingDateOnBroadway
Indicates the date on which a Broadway production ends its run and officially closes.
-
B.
closingOutcome
Indicates the result or consequence that follows from a closing action or the completion of a closure process between entities.
-
C.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
-
D.
dateFinalized
chosen
Indicates that a specific date has been set as the official or final completion/confirmation time for an associated event, decision, or record.
-
E.
collapseDate
Indicates the date on which something structurally or functionally failed, broke down, or ceased to exist.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99ac17a48190bb8448394f22b1e9 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.