Triple
T17178437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulko |
E416920
|
entity |
| Predicate | roleInAtlantis |
P126623
|
FINISHED |
| Object | royal advisor |
—
|
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: royal advisor | Statement: [Vulko, roleInAtlantis, royal advisor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAtlantis Context triple: [Vulko, roleInAtlantis, royal advisor]
-
A.
roleAtPluto
Indicates that an entity holds or held a specific role or position within the organization or project named Pluto.
-
B.
roleInElysium
Indicates that an entity holds a specific role, position, or function within the context of Elysium.
-
C.
roleInTauris
Indicates that an entity has a specific role or function within the context of Tauris (e.g., a work, setting, or domain associated with Tauris).
-
D.
roleInOrigin
Indicates that an entity holds or held a specific role, function, or position within the context of its origin or source.
-
E.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
- F. None of above. chosen
Provenance (4 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0ee5008190a73875b39841fd9f |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:37 a.m.