Triple
T4768335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michal |
E105865
|
entity |
| Predicate | usedObjectInRescue |
P50948
|
FINISHED |
| Object | household idol (teraphim) |
—
|
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: household idol (teraphim) | Statement: [Michal, usedObjectInRescue, household idol (teraphim)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedObjectInRescue Context triple: [Michal, usedObjectInRescue, household idol (teraphim)]
-
A.
usedResource
Indicates that an entity has utilized or consumed a particular resource in performing an action or achieving a result.
-
B.
usedMeansToRescue
chosen
Indicates that one entity employed a particular method, tool, or means in order to carry out a rescue.
-
C.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
D.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
-
E.
usedInCase
Indicates that something (such as an item, method, or piece of information) is employed or applied within a particular case or instance.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6537eb80819096e0ae906c59d605 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.