Triple
T38590100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elementium Reinforced Bulwark |
E932433
|
entity |
| Predicate | sourceBoss |
P409
|
FINISHED |
| Object | Halfus Wyrmbreaker |
—
|
NE NERFINISHED |
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: Halfus Wyrmbreaker | Statement: [Elementium Reinforced Bulwark, sourceBoss, Halfus Wyrmbreaker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceBoss Context triple: [Elementium Reinforced Bulwark, sourceBoss, Halfus Wyrmbreaker]
-
A.
personnelSource
Indicates the origin or provider from which personnel are obtained or assigned.
-
B.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
C.
hasBoss
Indicates that one entity serves as the direct superior or manager of another entity in a hierarchical relationship.
-
D.
sourceWorkSection
Indicates that one entity is a specific section or part extracted from a larger source work.
-
E.
targetsSource
Indicates that something is directed at, aimed toward, or focused on a specified source as its primary origin or object.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:32 p.m.