Triple
T38477565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyranny |
E915586
|
entity |
| Predicate | hasSkillSystem |
P121355
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tyranny, hasSkillSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkillSystem Context triple: [Tyranny, hasSkillSystem, true]
-
A.
hasSkillTree
chosen
Indicates that an entity is associated with a structured progression of skills or abilities, typically organized in a branching or hierarchical form.
-
B.
hasEponymousSkill
Indicates that an entity possesses a skill that is named after a particular person or entity.
-
C.
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.
-
D.
hasCraftingSystem
Indicates that an entity includes or supports a mechanism for creating or combining items, materials, or components into new objects or resources.
-
E.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.