Triple
T35564397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NE Division |
E1027727
|
entity |
| Predicate | teamGroupingType |
P93493
|
FINISHED |
| Object | geographic 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: geographic division | Statement: [NE Division, teamGroupingType, geographic division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamGroupingType Context triple: [NE Division, teamGroupingType, geographic division]
-
A.
groupingType
chosen
Indicates how multiple entities are categorized or clustered together based on a shared grouping criterion.
-
B.
movementGrouping
Indicates that multiple movements or motion events are treated as a single grouped or coordinated unit within a larger action or process.
-
C.
groupedInto
Indicates that multiple entities are collected or organized together as members of a common group or category.
-
D.
groupWithin
Indicates that one group is contained or nested as a subgroup within another, larger group.
-
E.
groupingRule
Indicates a rule or criterion that defines how multiple entities are grouped or clustered together based on shared characteristics or conditions.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.