Triple
T27667122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Stifle Tower |
E697255
|
entity |
| Predicate | associatedSkill |
P96902
|
FINISHED |
| Object | shot blocking |
—
|
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: shot blocking | Statement: [The Stifle Tower, associatedSkill, shot blocking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSkill Context triple: [The Stifle Tower, associatedSkill, shot blocking]
-
A.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
-
B.
skillSet
Indicates that an entity possesses or is associated with a particular collection of skills or competencies.
-
C.
indicatesSkill
chosen
Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another entity.
-
D.
killsAt
Indicates that one entity causes the death of another entity at a specific time or event.
-
E.
killsAsPartOfJob
Indicates that one entity kills another as a regular or expected duty within their professional role or occupation.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a00474f08908190bc8ae3b320ec887b |
completed | May 10, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_6a0045dc3bd48190a9e0520f3ef3f067 |
completed | May 10, 2026, 8:46 a.m. |
Created at: April 27, 2026, 2:39 p.m.