Triple

T24791636
Position Surface form Disambiguated ID Type / Status
Subject GTP E620265 entity
Predicate performanceTarget P80141 FINISHED
Object similar to former LMP2/LMP1 privateer pace 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: similar to former LMP2/LMP1 privateer pace | Statement: [GTP, performanceTarget, similar to former LMP2/LMP1 privateer pace]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: performanceTarget
Context triple: [GTP, performanceTarget, similar to former LMP2/LMP1 privateer pace]
  • A. optimizationTarget
    Indicates that one entity is the goal or objective that another entity is trying to improve, optimize, or make more efficient.
  • B. promotionTarget
    Indicates that one entity is the intended recipient or destination of a promotional action initiated by another entity.
  • C. performanceFocus
    Indicates that an entity directs attention or effort toward improving or emphasizing performance in a given context.
  • D. availabilityTarget
    Indicates that something is the intended object, resource, or condition whose availability is being specified, monitored, or constrained.
  • E. targetPerformanceLevel chosen
    Indicates the specific performance standard or level that an entity is expected or required to achieve.
  • 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_69e2fabe77c8819085f7ce6486248139 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f42d9000b8819081ea2605f3c193d6 completed May 1, 2026, 4:35 a.m.
PD Predicate disambiguation batch_69f420f471a0819095a6cd24ed8f7476 completed May 1, 2026, 3:41 a.m.
Created at: April 18, 2026, 4:47 a.m.