Triple
T15838545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köroghlu |
E384042
|
entity |
| Predicate | weaponInLegend |
P119851
|
FINISHED |
| Object | sword |
—
|
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: sword | Statement: [Köroghlu, weaponInLegend, sword]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponInLegend Context triple: [Köroghlu, weaponInLegend, sword]
-
A.
weaponForgedFor
Indicates that a weapon was specifically created or crafted for a particular entity, purpose, or context.
-
B.
weaponInOdyssey
Indicates that a given object functions as a weapon within the context of the Odyssey narrative.
-
C.
weaponInherited
Indicates that a weapon has been passed down or transferred from one entity to another as an inheritance.
-
D.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
E.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
- 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_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. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.