Triple

T4754370
Position Surface form Disambiguated ID Type / Status
Subject Petrovich E105551 entity
Predicate typicalPositionInFullName P32965 FINISHED
Object between given name and surname 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: between given name and surname | Statement: [Petrovich, typicalPositionInFullName, between given name and surname]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalPositionInFullName
Context triple: [Petrovich, typicalPositionInFullName, between given name and surname]
  • A. namePosition
    Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
  • B. fullName
    Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
  • C. typicalRecipientPosition
    Indicates the usual or expected spatial or organizational position where a recipient is located relative to the action or source.
  • D. namesakeFullName
    Indicates that one entity’s full name is used as the namesake or source of the name for another entity.
  • E. usedInFullNameOf chosen
    Indicates that one entity (such as a word, name part, or title) is used as a component within the complete formal name of another entity.
  • 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_69bd43f07fa48190954317d01600994a completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64e882b08190b100582e6d2e0334 completed March 20, 2026, 3:16 p.m.
PD Predicate disambiguation batch_69bd6223defc8190823665a6592c1154 completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:20 p.m.