Triple

T9978007
Position Surface form Disambiguated ID Type / Status
Subject Arverni E196379 entity
Predicate tributaryStatus P41038 FINISHED
Object subject to Rome after Gallic Wars 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: subject to Rome after Gallic Wars | Statement: [Arverni, tributaryStatus, subject to Rome after Gallic Wars]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tributaryStatus
Context triple: [Arverni, tributaryStatus, subject to Rome after Gallic Wars]
  • A. tributary
    Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
  • B. tributarySystem chosen
    Indicates a relationship where one political entity pays regular tribute or offers deference to another, acknowledging the latter’s superior authority or status.
  • C. isTributaryDamOf
    Indicates that a dam is constructed on and regulates the flow of a tributary river or stream relative to a main watercourse.
  • D. waterwayStatus
    Indicates the current navigational or operational condition of a waterway, such as whether it is open, restricted, or closed for use.
  • E. hasHeadwaterStatus
    Indicates that a water body holds the status of being a headwater or source segment within a hydrological system.
  • 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_69ca82efbce081908179b4b9c65096eb completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb84ef8ac8190abbe78b7611c5309 completed April 2, 2026, 12:29 a.m.
PD Predicate disambiguation batch_69cd1d9daa808190b413a1b9a1e929e2 completed April 1, 2026, 1:29 p.m.
Created at: March 30, 2026, 8:48 p.m.