Triple
T2195076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sultan of Swat |
E49952
|
entity |
| Predicate | describesSkill |
P36700
|
FINISHED |
| Object | home run hitting |
—
|
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: home run hitting | Statement: [The Sultan of Swat, describesSkill, home run hitting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesSkill Context triple: [The Sultan of Swat, describesSkill, home run hitting]
-
A.
requiresSkill
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
-
B.
validatesSkill
Indicates that one entity confirms or verifies the authenticity, correctness, or adequacy of another entity’s skill or competency.
-
C.
competenceArea
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
-
D.
trainedAs
Indicates that one entity has received education or instruction to perform the role, profession, or function represented by another entity.
-
E.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf764e348190896af2aeb5520038 |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbea8bd4881908f72019a5acf6174 |
completed | March 7, 2026, 5:59 a.m. |
Created at: March 4, 2026, 7:46 p.m.