Triple

T33052210
Position Surface form Disambiguated ID Type / Status
Subject Amo (Buccleuch motto) E845755 entity
Predicate tenseAndPerson P19255 FINISHED
Object first person singular present indicative 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: first person singular present indicative | Statement: [Amo (Buccleuch motto), tenseAndPerson, first person singular present indicative]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tenseAndPerson
Context triple: [Amo (Buccleuch motto), tenseAndPerson, first person singular present indicative]
  • A. grammaticalPersonOfVerb
    Indicates the grammatical person (first, second, or third person) associated with a given verb form.
  • B. hasTense
    Indicates that an action, event, or state is associated with a specific grammatical tense (such as past, present, or future).
  • C. grammaticalPerson
    Indicates the grammatical role of a participant in speech (such as first, second, or third person) in relation to the speaker and listener.
  • D. conjugationType
    Indicates the specific pattern or class of inflectional changes a verb follows when it is conjugated.
  • E. hasTenseAspect chosen
    Indicates that a verb or clause is associated with a specific grammatical tense and aspect configuration.
  • 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_69f3495242e48190996a2cb2beab5455 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d6a6b04c8190bee4cf9c00665ef7 completed May 3, 2026, 5:01 a.m.
PD Predicate disambiguation batch_69f6d27120988190aacec621cf2bf0e8 completed May 3, 2026, 4:43 a.m.
Created at: May 1, 2026, 1:24 a.m.