Triple
T3287009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charly Baltimore |
E69005
|
entity |
| Predicate | specialSkill |
P45342
|
FINISHED |
| Object | hand-to-hand combat |
—
|
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: hand-to-hand combat | Statement: [Charly Baltimore, specialSkill, hand-to-hand combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialSkill Context triple: [Charly Baltimore, specialSkill, hand-to-hand combat]
-
A.
skillEmphasis
chosen
Indicates that a particular skill is given special focus, priority, or importance within a context such as a role, task, or curriculum.
-
B.
kills
Indicates that one entity causes the death of another entity, ending its life.
-
C.
specialFeature
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
-
D.
specialValue
Indicates that an entity possesses a distinguished or exceptional value compared to typical or default values in the given context.
-
E.
perkType
Indicates the specific category or kind of benefit, bonus, or advantage associated with an entity or situation.
- 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb05779d08190a5517951e71b1380 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.