Triple
T1506628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Bulldogs |
E33914
|
entity |
| Predicate | playedAssociationFootball |
P29458
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Boston Bulldogs, playedAssociationFootball, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedAssociationFootball Context triple: [Boston Bulldogs, playedAssociationFootball, true]
-
A.
playedFor
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
B.
leaguePlayedIn
Indicates that a sports team or player has participated in competitions within a particular league.
-
C.
sportingAssociation
Indicates a formal relationship in which an organization serves as a governing, organizing, or affiliating body for sports activities, teams, or events.
-
D.
teamPlayedFor
Indicates that a person was a member of and played for a particular sports team.
-
E.
league2
Indicates that an entity participates in, is a member of, or is otherwise affiliated with a specific sports league or competitive organization.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90584b8b881908e112c7e59163812 |
completed | March 5, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69a88727ce48819089b482cdc25453d1 |
completed | March 4, 2026, 7:25 p.m. |
| PDg | Predicate description generation | batch_69a90582f2548190bc0a6bdcd6d9d015 |
completed | March 5, 2026, 4:24 a.m. |
Created at: March 4, 2026, 7:24 p.m.