Triple
T37953928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jab Jab |
E946811
|
entity |
| Predicate | usesPropFor |
P46693
|
FINISHED |
| Object | cracking whips |
—
|
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: cracking whips | Statement: [Jab Jab, usesPropFor, cracking whips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPropFor Context triple: [Jab Jab, usesPropFor, cracking whips]
-
A.
usesProp
chosen
Indicates that one entity employs, utilizes, or makes use of a particular property, resource, or object in performing an action or fulfilling a function.
-
B.
propUsed
Indicates that a particular property or attribute is utilized or applied in a given context or situation.
-
C.
supportsProp
Indicates that one entity provides assistance, endorsement, or backing for a particular property, attribute, or characteristic of another entity.
-
D.
appearsAsProp
Indicates that one entity is used or presented as a prop in relation to another entity or context.
-
E.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
- 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:20 p.m.