Triple
T33118262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dame Vaako |
E847516
|
entity |
| Predicate | rankWithinNecromongers |
P37057
|
FINISHED |
| Object | high-ranking noblewoman |
—
|
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: high-ranking noblewoman | Statement: [Dame Vaako, rankWithinNecromongers, high-ranking noblewoman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankWithinNecromongers Context triple: [Dame Vaako, rankWithinNecromongers, high-ranking noblewoman]
-
A.
necropolisRole
Indicates that an entity has a specific functional or social role in relation to a necropolis (a large cemetery or burial ground).
-
B.
rankAmongGods
Indicates how a being’s status or position compares relative to other gods within a divine hierarchy.
-
C.
hasRankAtDeath
Indicates the rank or position an entity held at the time of its death.
-
D.
chronRank
Indicates the relative chronological order or ranking of events or time-related entities with respect to one another.
-
E.
rankTier
chosen
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d716bb348190afff2f576d238e06 |
completed | May 3, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.