Triple
T29655108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archon |
E750242
|
entity |
| Predicate | requiresSacrificeOf |
P162223
|
FINISHED |
| Object | two High Templar |
—
|
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: two High Templar | Statement: [Archon, requiresSacrificeOf, two High Templar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSacrificeOf Context triple: [Archon, requiresSacrificeOf, two High Templar]
-
A.
requiresSacrifice
Indicates that the fulfillment or occurrence of one entity, condition, or action depends on giving up or losing another entity, resource, or value.
-
B.
demandedSacrifices
chosen
Indicates that one entity required or insisted that another entity offer sacrifices, typically as a condition, tribute, or act of devotion.
-
C.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
D.
sacrificeAcceptedBy
Indicates that a sacrificial offering made by one entity is received and deemed acceptable by another entity.
-
E.
sacrificeType
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: April 28, 2026, 6:54 p.m.