Triple
T25711426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anne |
E644740
|
entity |
| Predicate | hasCharacteristicFear |
P7327
|
FINISHED |
| Object | danger |
—
|
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: danger | Statement: [Anne, hasCharacteristicFear, danger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacteristicFear Context triple: [Anne, hasCharacteristicFear, danger]
-
A.
fearedAs
Indicates that one entity is regarded or perceived by another as an object of fear or intimidation.
-
B.
notableFear
chosen
Indicates that one entity is especially afraid of, or has a significant fear related to, another entity.
-
C.
fearMotive
Indicates that one entity’s actions or decisions are motivated by fear of another entity or of a particular outcome.
-
D.
fearExploitedBy
Indicates that one entity experiences fear as a result of being exploited, manipulated, or taken advantage of by another entity.
-
E.
hasHumanCharacteristic
Indicates that an entity possesses a trait, quality, or behavior typically associated with humans.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 9:14 p.m.