Triple

T37528060
Position Surface form Disambiguated ID Type / Status
Subject Fury E932957 entity
Predicate collectiveRomanName P172101 FINISHED
Object Furiae 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: Furiae | Statement: [Fury, collectiveRomanName, Furiae]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: collectiveRomanName
Context triple: [Fury, collectiveRomanName, Furiae]
  • A. romanNomen
    Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
  • B. collectivelyKnownAs
    Indicates that multiple entities are referred to together under a single shared name or designation.
  • C. collectiveNameForm chosen
    Indicates that one entity serves as the collective or group name form used to refer to multiple members of another entity or class.
  • D. romanCivitasName
    Indicates that an entity bears the official Roman civitas (city or community) name associated with it.
  • E. allyOfRome
    Indicates a relationship where one entity is politically or militarily aligned with, and offers support or cooperation to, Rome.
  • 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_69f76ec8862c8190bfa24145f5480642 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fe38be079c8190a240191ac0e73e3a completed May 8, 2026, 7:25 p.m.
PD Predicate disambiguation batch_69fe350344508190930de2218156ca02 completed May 8, 2026, 7:09 p.m.
Created at: May 3, 2026, 4:17 p.m.