Triple
T33571088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramsey (Fast & Furious) |
E859899
|
entity |
| Predicate | teamRoleInFastX |
P176897
|
FINISHED |
| Object | tech support for heists and missions |
—
|
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: tech support for heists and missions | Statement: [Ramsey (Fast & Furious), teamRoleInFastX, tech support for heists and missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamRoleInFastX Context triple: [Ramsey (Fast & Furious), teamRoleInFastX, tech support for heists and missions]
-
A.
lineupRole
Indicates the specific role or position an entity holds within a lineup or ordered group.
-
B.
roleAtSportsTeam
Indicates the specific position or function an individual holds within a sports team.
-
C.
teamNumberRole
Indicates that a specific team, identified by its number, is associated with a particular role or function.
-
D.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
E.
teamSuccessRole
Indicates the role or contribution an entity has in achieving or influencing a team's success.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:40 a.m.