Triple
T32535771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier 5 tournaments |
E831583
|
entity |
| Predicate | hadEventCode |
P174558
|
FINISHED |
| Object | Premier 5 |
—
|
NE NERFINISHED |
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: Premier 5 | Statement: [Premier 5 tournaments, hadEventCode, Premier 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadEventCode Context triple: [Premier 5 tournaments, hadEventCode, Premier 5]
-
A.
hadEvent
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
B.
hadListeningEventAt
Indicates that a listening event involving an entity occurred at a specific time or place.
-
C.
hasEventNumber
Indicates that an entity is associated with a specific event identified by a unique number.
-
D.
hasIneCode
Indicates that an entity is associated with a specific INE (national statistics or education) code that identifies it in an official registry.
-
E.
hasSideEvent
Indicates that an event is associated with an additional, related side event occurring alongside it.
- F. None of above. chosen
Provenance (4 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57062c481908b041788842c5990 |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:01 a.m.