Triple
T31914671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic League North Division |
E814794
|
entity |
| Predicate | hasConferenceOrDivisionRole |
P39861
|
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: [Atlantic League North Division, hasConferenceOrDivisionRole, North Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConferenceOrDivisionRole Context triple: [Atlantic League North Division, hasConferenceOrDivisionRole, North Division]
-
A.
hasConferenceOrDivision
chosen
Indicates that an entity is associated with a specific conference or division within a larger organizational or competitive structure.
-
B.
hasConferenceType
Indicates that an entity is associated with or classified by a specific type or category of conference.
-
C.
hasConference
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
D.
hasConferenceSport
Indicates that an institution participates in or is associated with a particular sport within a specific athletic conference.
-
E.
hasDivisionRole
Indicates that an entity holds a specific role or position within a particular division of an organization.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0338d1074481909541e6150307e7f8 |
completed | May 12, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_6a03386e7da08190b533cb0e908503dd |
completed | May 12, 2026, 2:25 p.m. |
Created at: May 1, 2026, 12:02 a.m.