Triple
T33772540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon Black |
E865419
|
entity |
| Predicate | hasPrimaryEventsRevolvingAround |
P203698
|
FINISHED |
| Object | Strange |
E246855
|
NE 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: Strange | Statement: [Canon Black, hasPrimaryEventsRevolvingAround, Strange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryEventsRevolvingAround Context triple: [Canon Black, hasPrimaryEventsRevolvingAround, Strange]
-
A.
hasRecreationEvent
Indicates that an entity is associated with, organizes, or participates in a recreational event or activity.
-
B.
hasPublicEventsIn
Indicates that an entity organizes or holds public events within a specified location or context.
-
C.
hasOccasionalEvent
Indicates that an event or activity occurs irregularly or infrequently in relation to a given entity or context.
-
D.
hasEventSeries
Indicates that an entity is associated with, or participates in, a sequence of related events forming a series.
-
E.
hasNotablePersonEvent
Indicates that there exists a significant event in which the person plays a notable or central role.
- F. None of above. chosen
Provenance (5 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01ca0db6f08190bed479584114e63d |
completed | May 11, 2026, 12:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3689bdc0f08190a65dbf042e5bf837 |
completed | June 20, 2026, 12:38 p.m. |
| PD | Predicate disambiguation | batch_6a01c96ff4a08190a4fbf0cebbda95b4 |
completed | May 11, 2026, 12:20 p.m. |
| PDg | Predicate description generation | batch_6a01ca0bf57881908d0dcfb2a25556b3 |
completed | May 11, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.