Triple

T28411248
Position Surface form Disambiguated ID Type / Status
Subject Picentine War E719666 entity
Predicate hasLanguageOfBelligerent P10179 FINISHED
Object Latin 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: Latin | Statement: [Picentine War, hasLanguageOfBelligerent, Latin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfBelligerent
Context triple: [Picentine War, hasLanguageOfBelligerent, Latin]
  • A. combatantLanguage chosen
    Indicates the language used by a combatant in a conflict or competitive interaction.
  • B. hasLanguageOfSide
    Indicates that an entity uses or is associated with a particular language on a specific side or aspect (e.g., one side of a bilingual object or interface).
  • C. hasLanguageOfMission
    Indicates that an entity (such as a mission or project) is associated with a specific language used for its communication, documentation, or operation.
  • D. hasLanguageOfSurroundingCountries
    Indicates that an entity uses or includes the languages commonly spoken in the countries that geographically surround it.
  • E. isLanguageOf
    Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
  • 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_69eff6f0f37c8190b37bc6fab08a9449 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69fcda3699948190adb57625bae08091 completed May 7, 2026, 6:30 p.m.
PD Predicate disambiguation batch_69fcd8fd16d08190b0aca6e19a632e99 completed May 7, 2026, 6:25 p.m.
Created at: April 28, 2026, 1:27 a.m.