Triple
T15309341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Division (Sun Belt Conference football) |
E365986
|
entity |
| Predicate | divisionOrientation |
P46580
|
FINISHED |
| Object | East |
—
|
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: East | Statement: [East Division (Sun Belt Conference football), divisionOrientation, East]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionOrientation Context triple: [East Division (Sun Belt Conference football), divisionOrientation, East]
-
A.
divisionRenamedFrom
Indicates that a division currently known by one name was previously known by another specified name.
-
B.
divisionPlacement
chosen
Indicates that one entity is assigned or positioned within a particular division or subgroup of another entity.
-
C.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
D.
divisionSince
Indicates that one entity has been divided or split from another starting at a specific point in time.
-
E.
divisionContext
Indicates the situational or conceptual setting in which a division operation or separation between entities takes place.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03cd176708190b0f6ba17aed92f8e |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.