Triple
T36957477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die, Führer, Die! |
E914223
|
entity |
| Predicate | containsPickup |
P203356
|
FINISHED |
| Object | keys for locked doors |
—
|
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: keys for locked doors | Statement: [Die, Führer, Die!, containsPickup, keys for locked doors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPickup Context triple: [Die, Führer, Die!, containsPickup, keys for locked doors]
-
A.
hasPickup
Indicates that one entity is assigned or associated with a specific pickup location, time, or arrangement for collection.
-
B.
usesPickupType
Indicates that one entity employs or operates a specific type of pickup in performing its function or action.
-
C.
hasNumberOfPickups
Indicates the quantity or count of pickup events or pickup items associated with an entity.
-
D.
pickupOption
Indicates that one entity offers or selects a method or arrangement for collecting or retrieving another entity (such as goods, items, or services).
-
E.
pickupType
Indicates the manner or method by which an item or person is collected or retrieved (e.g., in-store pickup, curbside, scheduled pickup).
- F. None of above. chosen
Provenance (4 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a016777257081908841c5522dfa76e6 |
completed | May 11, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_6a0164e49bec8190af3c8626be9677a9 |
completed | May 11, 2026, 5:11 a.m. |
| PDg | Predicate description generation | batch_6a016775df2c81909448a0201f5f4af6 |
completed | May 11, 2026, 5:21 a.m. |
Created at: May 3, 2026, 4:13 p.m.