Triple

T4139537
Position Surface form Disambiguated ID Type / Status
Subject Falisci E89237 entity
Predicate politicalStatusAfterConquest P32946 FINISHED
Object Roman allies 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: Roman allies | Statement: [Falisci, politicalStatusAfterConquest, Roman allies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: politicalStatusAfterConquest
Context triple: [Falisci, politicalStatusAfterConquest, Roman allies]
  • A. legalStatusAfterWar
    Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
  • B. afterConquestBy chosen
    Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
  • C. legalStatusAfterCoup
    Indicates the legal status or standing of an entity following a coup or unconstitutional change of power.
  • D. politicalStatusBeforeReign
    Indicates the political role or status an individual held prior to beginning their reign or period of rule.
  • E. conqueredInPartBy
    Indicates that one entity has gained control over a portion, but not the entirety, of another entity through conquest.
  • 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_69aed95785788190ae75bcf0cd1cafdf completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af03a0f3408190adba7a8513bd3d12 completed March 9, 2026, 5:30 p.m.
PD Predicate disambiguation batch_69af018a54848190987f18c066c75068 completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:43 p.m.