Triple
T10610667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High-A East |
E275996
|
entity |
| Predicate | divisionName |
P899
|
FINISHED |
| Object | North 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: North Division | Statement: [High-A East, divisionName, North Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionName Context triple: [High-A East, divisionName, North Division]
-
A.
divisionTitle
chosen
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
B.
divisionOrStructure
Indicates a relationship where one entity is an internal division, department, or structural subunit that is organizationally contained within another entity.
-
C.
regionDivision
Indicates a hierarchical or organizational subdivision relationship where one region is partitioned into smaller constituent regions.
-
D.
divisionPlacement
Indicates that one entity is assigned or positioned within a particular division or subgroup of another entity.
-
E.
divisionAssociation
Indicates an organizational relationship where one entity functions as a division, branch, or sub-unit 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df59468881909b0c67d3f08c4b76 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:32 p.m.