Triple
T20385922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulcan nerve pinch |
E497954
|
entity |
| Predicate | fandomTerm |
P139921
|
FINISHED |
| Object | neck pinch |
—
|
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: neck pinch | Statement: [Vulcan nerve pinch, fandomTerm, neck pinch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fandomTerm Context triple: [Vulcan nerve pinch, fandomTerm, neck pinch]
-
A.
fandomContext
Indicates that the relationship or action occurs specifically within the context of a particular fandom or fan community.
-
B.
fandomUses
Indicates that a fandom makes use of, relies on, or incorporates a particular resource, tool, platform, or element.
-
C.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
-
D.
fandomCharacteristic
Indicates that an entity possesses a particular trait, behavior, or quality specifically in the context of its fandom or fan community.
-
E.
fandomInterpretation
Indicates a relationship where an entity represents or expresses a fan-created interpretation, theory, or reading of another work or element within a fandom.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6790bcef481909453d19c846ab420 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:28 a.m.