Triple
T24801610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Rebels |
E620537
|
entity |
| Predicate | hasNoSuccessorTeam |
P162844
|
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: [Pittsburgh Rebels, hasNoSuccessorTeam, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoSuccessorTeam Context triple: [Pittsburgh Rebels, hasNoSuccessorTeam, true]
-
A.
hasSuccessorTeam
Indicates that one team is the direct successor or continuation of another team, typically following rebranding, relocation, or organizational change.
-
B.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
C.
hasCurrentTeam
Indicates that an entity is presently a member of or affiliated with a specific team.
-
D.
successorTeamLeague
Indicates that one sports league is the direct successor to another for a given team’s participation or affiliation.
-
E.
successorTeamInception
Indicates that one team was formed as the direct successor to another team at the time of its inception.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f62e83045c8190a424a2e401a88e9e |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d886828819080ec2f742b9449e3 |
completed | May 2, 2026, 4:59 p.m. |
Created at: April 18, 2026, 4:49 a.m.