Triple
T27739976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebellion |
E701825
|
entity |
| Predicate | hasSinglesDivision |
P175636
|
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: [Rebellion, hasSinglesDivision, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSinglesDivision Context triple: [Rebellion, hasSinglesDivision, yes]
-
A.
competesInDivision
Indicates that an entity participates in competitive activities within a specified division or tier of a larger organizational or league structure.
-
B.
isMultipleDivisionChampion
Indicates that an entity has won championship titles in more than one competitive division or category.
-
C.
hasBroadcastDivision
Indicates that an entity possesses or is associated with a specific division responsible for broadcasting activities.
-
D.
hasSecondDivision
Indicates that an entity possesses or is associated with a second-level division or subdivision within its structure or hierarchy.
-
E.
hasDivisionLevel
Indicates that one entity is associated with a specific hierarchical or organizational division level of another 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 27, 2026, 4:09 p.m.