Triple
T17356928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Division (WHL) |
E421959
|
entity |
| Predicate | memberOfStructure |
P24844
|
FINISHED |
| Object | WHL divisional alignment |
—
|
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: WHL divisional alignment | Statement: [Central Division (WHL), memberOfStructure, WHL divisional alignment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfStructure Context triple: [Central Division (WHL), memberOfStructure, WHL divisional alignment]
-
A.
memberOf
Indicates that an entity belongs to, is part of, or is a constituent of a larger group, organization, or collection.
-
B.
membershipStructure
chosen
Indicates the organizational or hierarchical arrangement that defines how members are grouped, related, and governed within a collective or system.
-
C.
memberOfGroupWith
Indicates that an entity belongs to, or is associated as a member with, a particular group or collection of entities.
-
D.
hasStructureRole
Indicates that an entity serves a specific functional or positional role within a larger structure or organizational arrangement.
-
E.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4976788190b00c00f710be6c46 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.