Triple
T1343836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leave It to Psmith |
E28524
|
entity |
| Predicate | featuresMotive |
P6699
|
FINISHED |
| Object | stolen necklace |
—
|
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: stolen necklace | Statement: [Leave It to Psmith, featuresMotive, stolen necklace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMotive Context triple: [Leave It to Psmith, featuresMotive, stolen necklace]
-
A.
featuresVehicle
Indicates that one entity includes, presents, or prominently incorporates a particular vehicle as part of its content, composition, or offering.
-
B.
motive
chosen
Indicates the underlying reason, intention, or driving force that explains why an entity performs or is associated with a particular action or event.
-
C.
equipmentCharacteristic
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
-
D.
featuresCross
Indicates that one feature or element intersects or passes across another in space or structure.
-
E.
transportCharacteristic
Indicates a relationship where a specific characteristic, property, or feature is attributed to a mode or instance of transport.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c23b8a9081908b78405d4ef806af |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.