Triple
T31885082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QubicaAMF Bowling World Cup |
E813985
|
entity |
| Predicate | hasSeparateDivision |
P90657
|
FINISHED |
| Object | men's division |
—
|
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: men's division | Statement: [QubicaAMF Bowling World Cup, hasSeparateDivision, men's division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeparateDivision Context triple: [QubicaAMF Bowling World Cup, hasSeparateDivision, men's division]
-
A.
containsDivision
chosen
Indicates that one entity includes or encompasses a subdivision or internal division of another entity.
-
B.
hasDivisionLevel
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
-
C.
hasDivisionNames
Indicates that an entity is associated with one or more names of its internal divisions or subunits.
-
D.
hasDivisionRule
Indicates that one entity is governed, organized, or separated according to a specified rule or method of division defined by another entity.
-
E.
hasFieldDivision
Indicates that one entity is organizationally divided into, or associated with, a specific field-based subdivision of another entity.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: April 30, 2026, 11:57 p.m.