Triple
T31283037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crix Madine |
E797725
|
entity |
| Predicate | statusInLegends |
P122936
|
FINISHED |
| Object | deceased |
—
|
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: deceased | Statement: [Crix Madine, statusInLegends, deceased]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInLegends Context triple: [Crix Madine, statusInLegends, deceased]
-
A.
isLegendaryStatus
Indicates that an entity possesses a legendary status, typically signifying exceptional rarity, renown, or significance within a given context.
-
B.
knownAsLegend
Indicates that an entity is widely regarded or celebrated as a legend.
-
C.
basedInLegend
Indicates that something is located, rooted, or primarily known within the context of a legend or mythic narrative.
-
D.
legendStatus
chosen
Indicates that an entity holds, is assigned, or is associated with a particular legend-related status or classification.
-
E.
statusInHagiography
Indicates the role or standing an individual holds within a hagiographic account (such as saint, author, subject, or related figure).
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 29, 2026, 9:13 p.m.