Triple
T35691664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamestown Falcons |
E1031307
|
entity |
| Predicate | usedLeagueNameUntil |
P84893
|
FINISHED |
| Object | PONY League 1956 |
—
|
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: PONY League 1956 | Statement: [Jamestown Falcons, usedLeagueNameUntil, PONY League 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLeagueNameUntil Context triple: [Jamestown Falcons, usedLeagueNameUntil, PONY League 1956]
-
A.
previousLeagueNameUsage
chosen
Indicates that an entity previously used a different league name during an earlier period or context.
-
B.
previousLeagueNameContext
Indicates that the predicate specifies the contextual information or circumstances under which a league previously had a particular name.
-
C.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed within a particular league.
-
D.
revertedLeagueName
Indicates that an entity’s league name has been changed back to a previous or original league name after a prior modification.
-
E.
namedAfterLeague
Indicates that one entity has been given a name derived from or in honor of a particular league.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.