Triple
T36956767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massive Chalice |
E914207
|
entity |
| Predicate | bloodlineAffects |
P143403
|
FINISHED |
| Object | hero traits |
—
|
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: hero traits | Statement: [Massive Chalice, bloodlineAffects, hero traits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bloodlineAffects Context triple: [Massive Chalice, bloodlineAffects, hero traits]
-
A.
hasBloodline
Indicates that one entity is ancestrally or genetically descended from, or belongs to the lineage of, another entity.
-
B.
basedOnCharacterLineage
Indicates that one entity is derived from, inspired by, or determined according to the ancestral or familial lineage of a character.
-
C.
bloodTrait
chosen
Indicates that one entity has a specific blood-related characteristic, property, or attribute associated with another entity.
-
D.
lineageRelatedTo
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
-
E.
heritageLine
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.