Triple
T29089999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valorant Protocol |
E734827
|
entity |
| Predicate | hasHighRankingMember |
P20032
|
FINISHED |
| Object | Viper |
—
|
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: Viper | Statement: [Valorant Protocol, hasHighRankingMember, Viper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighRankingMember Context triple: [Valorant Protocol, hasHighRankingMember, Viper]
-
A.
isHighRanking
Indicates that an entity holds a position of relatively great authority, status, or seniority within a hierarchy or organization.
-
B.
hasHonoraryMember
Indicates that an entity is recognized as an honorary (non-regular) member of another entity, typically without full rights or obligations of standard membership.
-
C.
hasRepresentativeRank
Indicates that an entity holds or is assigned a particular rank that serves as its official or primary representative status within a given context.
-
D.
admitsMemberRank
Indicates that an organization or group accepts individuals holding a specified rank or status as eligible members.
-
E.
hasCoreMember
chosen
Indicates that an entity includes another entity as a central or primary member of its group, organization, or structure.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 28, 2026, 11:04 a.m.