Triple
T6100149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Man of the Sea |
E135972
|
entity |
| Predicate | methodOfControl |
P43307
|
FINISHED |
| Object | locking his legs around the victim’s neck |
—
|
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: locking his legs around the victim’s neck | Statement: [Old Man of the Sea, methodOfControl, locking his legs around the victim’s neck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfControl Context triple: [Old Man of the Sea, methodOfControl, locking his legs around the victim’s neck]
-
A.
controlMethods
chosen
Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of another entity.
-
B.
rangeControlledBy
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
C.
typeOfControl
Indicates the specific manner or mechanism by which one entity exercises control or influence over another.
-
D.
methodologyType
Indicates the specific kind or category of method or procedure used in carrying out an activity or study.
-
E.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b3970808190ba90f5e4235db9f2 |
completed | March 22, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.