Triple
T35527506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul E. Dangerously |
E1026710
|
entity |
| Predicate | managedTagTeam |
P3239
|
FINISHED |
| Object | The Dangerous Alliance |
—
|
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 Dangerous Alliance | Statement: [Paul E. Dangerously, managedTagTeam, The Dangerous Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managedTagTeam Context triple: [Paul E. Dangerously, managedTagTeam, The Dangerous Alliance]
-
A.
managedTeam
Indicates that one entity had responsibility for directing, supervising, and coordinating the work of another group or team.
-
B.
teamTag
Indicates that an entity is associated with, labeled by, or belongs to a particular team.
-
C.
hasTagTeamType
Indicates that an entity participates in or is associated with a specific type or category of tag team.
-
D.
twinTagTeam
Indicates a cooperative relationship where two twin entities act together as a coordinated team in performing an action or achieving a goal.
-
E.
managedTeamTo
chosen
Indicates that one entity had managerial responsibility or oversight over the specified team.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.