Triple
T35009148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lionheart: Legacy of the Crusader |
E1009899
|
entity |
| Predicate | usesRuleSystemInspiredBy |
P6249
|
FINISHED |
| Object | SPECIAL system |
—
|
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: SPECIAL system | Statement: [Lionheart: Legacy of the Crusader, usesRuleSystemInspiredBy, SPECIAL system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRuleSystemInspiredBy Context triple: [Lionheart: Legacy of the Crusader, usesRuleSystemInspiredBy, SPECIAL system]
-
A.
usesRulesFrom
chosen
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
B.
rulesSystem
Indicates that an entity establishes, governs, or defines the rules or structure by which another system or process operates.
-
C.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
D.
assumedRuleOf
Indicates that one entity is presumed or taken to hold authoritative control, governance, or dominion over another entity, typically without definitive confirmation.
-
E.
isRuleGoverned
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:01 p.m.