Triple
T34473741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International League East Division |
E884974
|
entity |
| Predicate | regionalAlignment |
P86279
|
FINISHED |
| Object | East |
—
|
NE NERFINISHED |
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: [International League East Division, regionalAlignment, East]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalAlignment Context triple: [International League East Division, regionalAlignment, East]
-
A.
countryAlignment
Indicates the geopolitical or ideological stance of a country in relation to other countries, blocs, or global power structures.
-
B.
regionalOrientation
chosen
Indicates how something is directed, aligned, or focused toward a particular geographic region or area.
-
C.
countryRegionalOrganization
Indicates that a country is a member of, or affiliated with, a specific regional organization.
-
D.
politicalRegionType
Indicates the classification of a political region according to its governmental or administrative type (e.g., state, province, municipality).
-
E.
regionalGrouping
Indicates that entities are organized or associated together based on shared geographic or regional characteristics.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 1, 2026, 2:01 a.m.