Triple
T7090697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Legion World Series |
E165185
|
entity |
| Predicate | teamOrigin |
P74477
|
FINISHED |
| Object | across the United States |
—
|
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: across the United States | Statement: [American Legion World Series, teamOrigin, across the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamOrigin Context triple: [American Legion World Series, teamOrigin, across the United States]
-
A.
originLeague
Indicates the sports league or competition from which an entity (such as a team, player, or event) originally comes or is associated.
-
B.
committeeOfOrigin
Indicates the committee in which a proposal, bill, or item was first introduced or initially considered.
-
C.
teamRelocatedFrom
Indicates that a team previously based in one location has moved its home base or operations from that original location to a different one.
-
D.
formerLeagueTeam
Indicates that an entity was previously a member team of a particular sports league but is no longer part of that league.
-
E.
formerTeam2Name
Indicates that an entity was previously associated with a second former team identified by this name.
- F. None of above. chosen
Provenance (4 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e53012b081908bf40541d85c82f1 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e24af9ac8190b24eee206ba8be36 |
completed | March 27, 2026, 8:02 p.m. |
Created at: March 27, 2026, 2:41 p.m.