Triple
T31824520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romeo |
E812353
|
entity |
| Predicate | teamOpposed |
P172640
|
FINISHED |
| Object | PJ Masks |
—
|
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: PJ Masks | Statement: [Romeo, teamOpposed, PJ Masks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamOpposed Context triple: [Romeo, teamOpposed, PJ Masks]
-
A.
teamOpponent
Indicates that two teams are competing against each other as opponents in a game or match.
-
B.
rivalTeam
Indicates that one team is in a competitive or adversarial relationship with another team, often vying for superiority or dominance.
-
C.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
D.
teamContestedBy
Indicates that a team participates as a competitor or contestant in a particular event, match, or competition.
-
E.
opponentTeamsAffected
Indicates that the specified action, condition, or effect applies to the teams designated as opponents.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b034bc74819091250f91ba5174c0 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:46 p.m.