Triple
T25071681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revis Island |
E627929
|
entity |
| Predicate | perceptionByOpponents |
P138559
|
FINISHED |
| Object | difficult matchup for elite wide receivers |
—
|
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: difficult matchup for elite wide receivers | Statement: [Revis Island, perceptionByOpponents, difficult matchup for elite wide receivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceptionByOpponents Context triple: [Revis Island, perceptionByOpponents, difficult matchup for elite wide receivers]
-
A.
perceivedByRivalsAs
chosen
Indicates that one entity is regarded or viewed in a particular way by its rivals.
-
B.
hasOppositionalPerception
Indicates that one entity perceives another entity, concept, or situation as being in opposition, conflict, or contradiction to itself or its interests.
-
C.
sawOpponentsAs
Indicates perceiving or regarding certain entities as opponents or adversaries.
-
D.
consideredOpponentsAs
Indicates that one entity regarded or treated another entity as an opponent or adversary.
-
E.
hasFanPerception
Indicates that an entity is perceived, interpreted, or regarded in a particular way by its fans or fan community.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:13 a.m.