Triple
T4870569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boomerang |
E109075
|
entity |
| Predicate | launchDateAsProgrammingBlock |
P180
|
FINISHED |
| Object | December 8, 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: December 8, 1992 | Statement: [Boomerang, launchDateAsProgrammingBlock, December 8, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchDateAsProgrammingBlock Context triple: [Boomerang, launchDateAsProgrammingBlock, December 8, 1992]
-
A.
launchDate
chosen
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
B.
launchDateNote
Indicates a note or qualifier providing additional information or context about an entity’s launch date.
-
C.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
-
D.
betaReleaseDate
Indicates the date on which a product or system is first released in its beta version for testing or limited use.
-
E.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c28e56081908ee411ac94c3769e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.