Triple
T19656256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Kentucky Norse |
E471950
|
entity |
| Predicate | fullDivisionIMembership |
P27891
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Northern Kentucky Norse, fullDivisionIMembership, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullDivisionIMembership Context triple: [Northern Kentucky Norse, fullDivisionIMembership, 2016]
-
A.
membershipIn
chosen
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
B.
membershipConsistsOf
Indicates that a membership is composed of, or includes, specific member entities as its constituents.
-
C.
hasDivisionRole
Indicates that an entity holds a specific role or position within a particular division of an organization.
-
D.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
E.
includeMember
Indicates that one entity contains or has another entity as a member or part of its composition.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64146539c8190813debb0d964bc23 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.