Triple
T7699812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Conference (no divisions) |
E174460
|
entity |
| Predicate | usesDivisions |
P29727
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Western Conference (no divisions), usesDivisions, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDivisions Context triple: [Western Conference (no divisions), usesDivisions, no]
-
A.
includesDivisions
chosen
Indicates that one entity contains or encompasses one or more subordinate divisions or sections within it.
-
B.
usedByDivision
Indicates that something (such as a resource, tool, or asset) is utilized or employed by a particular division within an organization.
-
C.
isPartOfDivision
Indicates that one entity belongs to, or is contained within, a specific division of a larger organizational or structural unit.
-
D.
differsByDivision
Indicates that two entities are distinct from each other specifically due to differences in how they are divided, partitioned, or segmented.
-
E.
usesAdministrativeDivisionType
Indicates that one entity employs or applies a particular type of administrative division as part of its territorial or organizational structure.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.