Triple
T26346376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Extreme |
E662785
|
entity |
| Predicate | associatedTagTeam |
P199012
|
FINISHED |
| Object | The Hardy Boyz |
—
|
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: The Hardy Boyz | Statement: [Team Extreme, associatedTagTeam, The Hardy Boyz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTagTeam Context triple: [Team Extreme, associatedTagTeam, The Hardy Boyz]
-
A.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
-
B.
teamTag
Indicates that an entity is associated with, labeled by, or belongs to a particular team.
-
C.
associatedTeamName
Indicates the name of the team that is linked or connected to a given entity.
-
D.
associatedSeniorTeam
Indicates a relationship where a senior-level team is linked or connected to a given entity as its corresponding or responsible team.
-
E.
associatedLeagueTeam
Indicates that one entity is a sports team that is formally linked or affiliated with a particular league.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69ff1ba7494481908678a7a0f93dbd03 |
completed | May 9, 2026, 11:33 a.m. |
Created at: April 26, 2026, 10:42 p.m.