Triple
T25475915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBA featherweight world champion |
E638432
|
entity |
| Predicate | hasMultipleVersionsPossible |
P28478
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [WBA featherweight world champion, hasMultipleVersionsPossible, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleVersionsPossible Context triple: [WBA featherweight world champion, hasMultipleVersionsPossible, yes]
-
A.
hasMultipleVersions
chosen
Indicates that an entity exists in more than one distinct version or revision.
-
B.
hasLiveVersions
Indicates that an entity has one or more recorded or documented live-performance versions of itself.
-
C.
hasVersionCount
Indicates the total number of distinct versions associated with a given entity.
-
D.
hasDiscreteVersion
Indicates that one entity exists as a specific, separate version or edition of another entity.
-
E.
hasSubsequentVersion
Indicates that one entity is a later or updated version that follows another entity in a version sequence.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 2:26 p.m.