Triple
T1434085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Lightweight Title |
E30517
|
entity |
| Predicate | canBeUnifiedWith |
P402
|
FINISHED |
| Object | other world lightweight titles |
—
|
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: other world lightweight titles | Statement: [World Lightweight Title, canBeUnifiedWith, other world lightweight titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUnifiedWith Context triple: [World Lightweight Title, canBeUnifiedWith, other world lightweight titles]
-
A.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
B.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
-
C.
hasUnionRepresentation
Indicates that an entity is represented by a labor union in negotiations or employment-related matters.
-
D.
formedByUnionOf
chosen
Indicates that something is created or defined as the union or combination of multiple other things.
-
E.
consolidatedAs
Indicates that one entity has been combined, merged, or unified into another entity to form a single consolidated whole.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.