Triple
T35011360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orcs |
E1009945
|
entity |
| Predicate | typicalWeaponStyle |
P7745
|
FINISHED |
| Object | Orcish weapons |
—
|
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: Orcish weapons | Statement: [Orcs, typicalWeaponStyle, Orcish weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWeaponStyle Context triple: [Orcs, typicalWeaponStyle, Orcish weapons]
-
A.
typicalWeapon
chosen
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
B.
tacticalStyle
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
C.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
D.
weaponDiscipline
Indicates that an entity practices, adheres to, or is governed by a particular system, style, or code of weapon use or combat training.
-
E.
shootingStyle
Indicates the characteristic manner or technique with which an entity performs a shooting action (e.g., in sports or photography).
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.