Triple
T29139301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Needler |
E738582
|
entity |
| Predicate | loreMaterial |
P47718
|
FINISHED |
| Object | crystal shards from Covenant-sourced materials |
—
|
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: crystal shards from Covenant-sourced materials | Statement: [Needler, loreMaterial, crystal shards from Covenant-sourced materials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loreMaterial Context triple: [Needler, loreMaterial, crystal shards from Covenant-sourced materials]
-
A.
materialInLore
chosen
Indicates that a material is referenced, described, or plays a role within a body of lore or fictional/worldbuilding context.
-
B.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
C.
crestMaterial
Indicates that one entity is the material from which another entity’s crest is made.
-
D.
material
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
-
E.
eraOfMaterial
Indicates the historical or geological era during which a given material originated, was formed, or was predominantly used.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6626dee588190ae10942e2a9bff64 |
completed | May 2, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:35 a.m.