Triple
T1094401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NABC All-District Teams |
E24238
|
entity |
| Predicate | usesUnitOfDivision |
P18043
|
FINISHED |
| Object | NABC geographic districts |
—
|
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: NABC geographic districts | Statement: [NABC All-District Teams, usesUnitOfDivision, NABC geographic districts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesUnitOfDivision Context triple: [NABC All-District Teams, usesUnitOfDivision, NABC geographic districts]
-
A.
unitOfMeasure
Indicates that one entity specifies the standard unit in which the quantity or value of another entity is measured.
-
B.
usesDivisionSystem
chosen
Indicates that one entity organizes or structures something by applying a particular system of division or categorization.
-
C.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
-
D.
minorUnitUsage
Indicates how a minor or subordinate unit is used or functions in relation to a larger or primary unit.
-
E.
usesDivisor
Indicates that one entity employs another entity as a divisor in a division or modular arithmetic operation.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99d1e8c81909cf1178d68d38885 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b743175481908f3967e589717c55 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.