Triple
T4979972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | chopchop attack |
E111859
|
entity |
| Predicate | feedbackSource |
P409
|
FINISHED |
| Object | access point acceptance or rejection |
—
|
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: access point acceptance or rejection | Statement: [chopchop attack, feedbackSource, access point acceptance or rejection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feedbackSource Context triple: [chopchop attack, feedbackSource, access point acceptance or rejection]
-
A.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
B.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
C.
criticizesSource
Indicates that one entity expresses disapproval of, or negative judgment about, the content, behavior, or credibility of another entity that is treated as a source.
-
D.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
E.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
- 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_69bd441adc208190b70a033a0741d01e |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.