Triple
T8249698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monsieur G—— |
E192925
|
entity |
| Predicate | failsToFind |
P30122
|
FINISHED |
| Object | the purloined letter |
—
|
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: the purloined letter | Statement: [Monsieur G——, failsToFind, the purloined letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failsToFind Context triple: [Monsieur G——, failsToFind, the purloined letter]
-
A.
finds
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
-
B.
containsFinding
Indicates that one entity includes, encompasses, or holds a particular finding as part of its content or results.
-
C.
failedOn
chosen
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
D.
foundAfter
Indicates that one entity is discovered or located at a point in time later than another specified entity.
-
E.
requiresFinding
Indicates that one entity’s validity, execution, or completion is contingent upon a specific finding or determination being made about another entity.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78c817708190ad1c364e12083d26 |
completed | March 31, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.