Triple
T35527454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sable Bomb |
E1026708
|
entity |
| Predicate | usedInDivision |
P31577
|
FINISHED |
| Object | WWE women’s division |
—
|
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: WWE women’s division | Statement: [Sable Bomb, usedInDivision, WWE women’s division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDivision Context triple: [Sable Bomb, usedInDivision, WWE women’s division]
-
A.
usedByDivision
chosen
Indicates that something (such as a resource, tool, or asset) is utilized or employed by a particular division within an organization.
-
B.
usedDivision
Indicates that one entity employed or applied a particular division (such as a subgroup, department, or partition) in performing an action or fulfilling a function.
-
C.
isPartOfDivision
Indicates that one entity belongs to, or is contained within, a specific division of a larger organizational or structural unit.
-
D.
containsDivision
Indicates that one entity includes or encompasses a subdivision or internal division of another entity.
-
E.
usedInDistrict
Indicates that something is utilized, applied, or implemented within the boundaries or jurisdiction of a specific district.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:04 p.m.