Triple
T22081884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appalachian League (summer collegiate) |
E545668
|
entity |
| Predicate | hasDivisions |
P29727
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Appalachian League (summer collegiate), hasDivisions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDivisions Context triple: [Appalachian League (summer collegiate), hasDivisions, true]
-
A.
hasDivisionLevel
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
-
B.
includesDivisions
chosen
Indicates that one entity contains or encompasses one or more subordinate divisions or sections within it.
-
C.
hasDivisionNames
Indicates that an entity is associated with one or more names of its internal divisions or subunits.
-
D.
containsDivision
Indicates that one entity includes or encompasses a subdivision or internal division of another entity.
-
E.
hasNumberOfDivisions
Indicates the relationship that specifies how many divisions or subunits an entity possesses.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b706288190945c0c37e5ff2756 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:28 p.m.