Triple
T29297043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darth Bane |
E742860
|
entity |
| Predicate | ruleOfTwoFormula |
P83057
|
FINISHED |
| Object | One to embody power and one to crave it |
—
|
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: One to embody power and one to crave it | Statement: [Darth Bane, ruleOfTwoFormula, One to embody power and one to crave it]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleOfTwoFormula Context triple: [Darth Bane, ruleOfTwoFormula, One to embody power and one to crave it]
-
A.
ruleOfTwoFormulatedBy
Indicates that an individual is the originator or creator of the "Rule of Two" principle or doctrine.
-
B.
ruleOfTwoDescription
chosen
Indicates that one entity provides a description or explanation of the "Rule of Two" principle that governs a specific two-member relationship or structure.
-
C.
countingRule
Indicates the rule or method used to count or quantify items, events, or entities in a given context.
-
D.
isReferenceCounted
Indicates that an entity’s lifetime or validity is managed by tracking how many active references or users it currently has.
-
E.
hasTwoClasses
Indicates that an entity is associated with exactly two distinct classes or categories.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6654459b481908684b3efa19d5bd5 |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 1:07 p.m.