Triple
T7766381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen Thompson |
E176156
|
entity |
| Predicate | hasStance |
P8071
|
FINISHED |
| Object | side-on karate stance |
—
|
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: side-on karate stance | Statement: [Stephen Thompson, hasStance, side-on karate stance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStance Context triple: [Stephen Thompson, hasStance, side-on karate stance]
-
A.
hasFightingStance
chosen
Indicates that an entity adopts or is characterized by a particular combat or fighting posture.
-
B.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
-
C.
hasAuthorialStance
Indicates that an entity expresses, embodies, or is associated with a particular author’s viewpoint, attitude, or perspective toward its subject matter.
-
D.
isStandOf
Indicates that one entity serves as the Stand (a supernatural or personified power) belonging to or associated with another entity.
-
E.
hasUserAttitude
Indicates that one entity holds a particular attitude, opinion, or evaluative stance toward another entity or subject.
- 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_69c69962923c8190ac74d28b4f9fe0a0 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7043451bc8190a76ee066b779b7d7 |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:10 p.m.