Triple
T17335335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabine Wren |
E420920
|
entity |
| Predicate | forceSensitivity |
P77486
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sabine Wren, forceSensitivity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forceSensitivity Context triple: [Sabine Wren, forceSensitivity, yes]
-
A.
forceSensitive
chosen
Indicates that an entity has an innate connection to and ability to perceive or use a mystical or supernatural energy or power.
-
B.
sensitivityFeature
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
-
C.
forceType
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
D.
sensitivityRegion
Indicates the specific area or domain within which a subject is particularly responsive, vulnerable, or reactive to a given influence or condition.
-
E.
timeSensitivity
Indicates how strongly the relationship or action depends on, changes with, or is constrained by time.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a1125d88190b67243b30d93ce1c |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.