Triple
T15838539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köroghlu |
E384042
|
entity |
| Predicate | hasOccupationInLegend |
P69186
|
FINISHED |
| Object | warrior |
—
|
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: warrior | Statement: [Köroghlu, hasOccupationInLegend, warrior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOccupationInLegend Context triple: [Köroghlu, hasOccupationInLegend, warrior]
-
A.
hasOccupationDuringStory
chosen
Indicates that an entity holds or performs a particular occupation or job role during the time span covered by the story.
-
B.
hasOccupationTheme
Indicates that something (such as a work or resource) centrally involves or focuses on a particular occupation or type of work as its main theme.
-
C.
hasOccupationRelative
Indicates that one entity has another entity as a relative who holds a particular occupation or job.
-
D.
hasHumanOccupationEvidence
Indicates that there is supporting evidence that a human has held or currently holds a particular occupation or job role.
-
E.
hasOccupationOfDesignee
Indicates that one entity serves as the designated or appointed holder of an occupation or role for another entity.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e4fa24819086a1a226082ac2d3 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.