Triple
T1452836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Welterweight Title |
E31331
|
entity |
| Predicate | unificationPossible |
P28768
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [World Welterweight Title, unificationPossible, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unificationPossible Context triple: [World Welterweight Title, unificationPossible, true]
-
A.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
B.
unificationAct
Indicates the formal joining or merging of previously separate entities into a single unified whole.
-
C.
hasCurrencyUnion
Indicates that two or more entities share a common official currency through a formal monetary or currency union.
-
D.
inUnionFlagRepresents
Indicates that one entity is represented or symbolized by its inclusion on the union flag of another entity.
-
E.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57d34cc8190801b769d9d9b2e2e |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c55508948190922aee3230a4323e |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8 p.m.