Triple
T35807424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rated-RKO |
E1035135
|
entity |
| Predicate | memberLaterTeamedAs |
P39081
|
FINISHED |
| Object | Rated-RKO reunion (sporadic) |
—
|
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: Rated-RKO reunion (sporadic) | Statement: [Rated-RKO, memberLaterTeamedAs, Rated-RKO reunion (sporadic)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberLaterTeamedAs Context triple: [Rated-RKO, memberLaterTeamedAs, Rated-RKO reunion (sporadic)]
-
A.
memberTeamAtVariousTimes
chosen
Indicates that an entity has been a member of a particular team during one or more distinct time periods.
-
B.
memberTeam
Indicates that an entity belongs to or is part of a specific team.
-
C.
becameWorksTeamOf
Indicates that one entity transitioned into serving as the work team for another entity.
-
D.
hasFormerTeam
Indicates that an entity was previously a member of, played for, or was affiliated with a team in the past but is no longer associated with that team.
-
E.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:06 p.m.