Triple

T33350073
Position Surface form Disambiguated ID Type / Status
Subject Eugene Kittridge E853909 entity
Predicate goalInDeadReckoning P176528 FINISHED
Object secure control over the Entity 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: secure control over the Entity | Statement: [Eugene Kittridge, goalInDeadReckoning, secure control over the Entity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: goalInDeadReckoning
Context triple: [Eugene Kittridge, goalInDeadReckoning, secure control over the Entity]
  • A. distanceFromGoal
    Indicates the measured or estimated separation between an entity’s current position and its intended goal or target state.
  • B. goalState
    Indicates the desired or target condition that an entity or system aims to reach or achieve.
  • C. goalAtEnd
    Indicates that a particular goal or objective holds true or is achieved at the final state or endpoint of a process, sequence, or event.
  • D. goalIn
    Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
  • E. machineGoal
    Indicates that a machine or automated system has a specific objective, target state, or outcome it is intended or programmed to achieve.
  • F. None of above. chosen

Provenance (4 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_69f3496acbc8819099fd0305ecc42080 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e3156ea48190b604e414665ef351 completed May 3, 2026, 5:54 a.m.
PD Predicate disambiguation batch_69f6de0b9ba48190887c9eb5d06a2e94 completed May 3, 2026, 5:32 a.m.
PDg Predicate description generation batch_69f6e312d7fc819094dec41810f2585d completed May 3, 2026, 5:54 a.m.
Created at: May 1, 2026, 1:34 a.m.