Triple
T37470733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikanikos |
E931144
|
entity |
| Predicate | hasLoreRole |
P200537
|
FINISHED |
| Object | Kyrian steward inventor |
—
|
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: Kyrian steward inventor | Statement: [Mikanikos, hasLoreRole, Kyrian steward inventor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoreRole Context triple: [Mikanikos, hasLoreRole, Kyrian steward inventor]
-
A.
hasRitualRoleIn
Indicates that an entity serves a specific ritual function or role within a particular ritual, ceremony, or sacred practice.
-
B.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
C.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
D.
hasRoleCharacteristic
Indicates that an entity possesses a specific characteristic, quality, or attribute associated with a particular role.
-
E.
mayHaveRole
Indicates that an entity is permitted or eligible to hold or perform a specified role.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
| PDg | Predicate description generation | batch_69ff935f48808190aa6f4834f59d45b8 |
completed | May 9, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.