Triple
T24405383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FCW |
E615295
|
entity |
| Predicate | hadChampionship |
P313
|
FINISHED |
| Object | FCW Florida Heavyweight Championship |
—
|
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: FCW Florida Heavyweight Championship | Statement: [FCW, hadChampionship, FCW Florida Heavyweight Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadChampionship Context triple: [FCW, hadChampionship, FCW Florida Heavyweight Championship]
-
A.
hasChampionships
chosen
Indicates that one entity possesses or has won one or more championships associated with another entity.
-
B.
hasWorldChampionship
Indicates that an entity possesses, has won, or holds a world championship title or status.
-
C.
championshipHeld
Indicates that a championship event took place or was hosted at a particular time and/or location.
-
D.
hasChampionshipMatch
Indicates that an entity is associated with a specific championship-level match, typically as an organizer, participant, or host.
-
E.
hasWonMultipleChampionships
Indicates that the subject has secured championship titles on more than one separate occasion.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294de76848190bd2cf3c7add2dcf1 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.