Triple

T18887671
Position Surface form Disambiguated ID Type / Status
Subject bow of Heracles E461997 entity
Predicate locationDuringTrojanWar P95771 FINISHED
Object Lemnos NE NERFINISHED

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: Lemnos | Statement: [bow of Heracles, locationDuringTrojanWar, Lemnos]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locationDuringTrojanWar
Context triple: [bow of Heracles, locationDuringTrojanWar, Lemnos]
  • A. goalInTrojanWar
    Indicates that an entity’s objective, aim, or purpose is specifically directed toward or realized within the context of the Trojan War.
  • B. takesSideInTrojanWar
    Indicates that an entity participates in the Trojan War as a supporter of one of the opposing sides.
  • C. mythologicalLocation
    Indicates that the subject is a place or setting that exists within mythology, legends, or folklore rather than in historical or physical reality.
  • D. locatedOnSideOfGreekMainland
    Indicates that one place is situated on the side of the Greek mainland relative to another reference point or area.
  • E. locationDuringConflict chosen
    Indicates that an entity is situated in a specific place for some or all of the duration of a particular conflict or hostilities.
  • 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_69d8dcfc3430819095ee6fc0eb4c06a5 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c4777434819098850da0ee1c6b43 completed April 20, 2026, 6:15 a.m.
PD Predicate disambiguation batch_69e4a2e27e1481908a8da10b28f07875 completed April 19, 2026, 9:39 a.m.
Created at: April 10, 2026, 11:58 a.m.