Triple
T37467707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resistance |
E931071
|
entity |
| Predicate | hasHandheldEntry |
P188372
|
FINISHED |
| Object | Resistance: Retribution |
—
|
NE NERFINISHED |
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: Resistance: Retribution | Statement: [Resistance, hasHandheldEntry, Resistance: Retribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHandheldEntry Context triple: [Resistance, hasHandheldEntry, Resistance: Retribution]
-
A.
supportsHandheldMode
Indicates that an entity is capable of operating or being used in a handheld mode.
-
B.
hasPocketType
Indicates the specific style or configuration of pocket associated with an item or garment.
-
C.
hasHolderCharacteristic
Indicates that a holder (such as an owner, container, or bearer) possesses or exhibits a particular characteristic or attribute.
-
D.
hasHeldBy
Indicates that one entity has been physically or conceptually grasped, possessed, or kept in the control of another entity.
-
E.
hasHolding
Indicates that one entity possesses, controls, or maintains ownership or custody of another entity as an asset or item.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.