Triple
T19942919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PostSecret |
E479350
|
entity |
| Predicate | usesAnonymity |
P111104
|
FINISHED |
| Object | no sender identification on postcards |
—
|
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: no sender identification on postcards | Statement: [PostSecret, usesAnonymity, no sender identification on postcards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAnonymity Context triple: [PostSecret, usesAnonymity, no sender identification on postcards]
-
A.
anonymityFunction
chosen
Indicates a function or mechanism that preserves or enforces anonymity in the relationship or interaction between entities.
-
B.
soughtPrivacy
Indicates that an entity intentionally attempted to obtain or maintain privacy from others.
-
C.
usesModeForConfidentiality
Indicates that an entity employs a particular mode, method, or mechanism specifically to ensure or enhance the confidentiality of information.
-
D.
usesSuperheroIdentity
Indicates that an entity adopts or operates under a superhero persona or alias, rather than their ordinary identity.
-
E.
usesTunnelOrBridge
Indicates that one entity travels or passes between locations by means of a tunnel or a bridge.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a63f2e48190ba1cb7a4f415e7f6 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.