Triple

T8816767
Position Surface form Disambiguated ID Type / Status
Subject ALPN E209795 entity
Predicate statusComparedToNPN P84783 FINISHED
Object standardized successor 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: standardized successor | Statement: [ALPN, statusComparedToNPN, standardized successor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statusComparedToNPN
Context triple: [ALPN, statusComparedToNPN, standardized successor]
  • A. featureLevelComparedTo
    Indicates a comparative relationship between entities based on their feature level, specifying how one entity’s feature level ranks relative to another’s.
  • B. technologyLevelComparedToPredecessor
    Indicates how the technology level of an entity compares to that of its immediate predecessor.
  • C. isStrongerProtectionThan
    Indicates that one form of protection provides a higher level of security, defense, or safeguarding compared to another.
  • D. comparisonType
    Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
  • E. scaleComparison
    Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
  • 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_69ca8364e13081909c85fe80f44fe86f completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc600bd8a88190ad891a96201d796b completed April 1, 2026, midnight
PD Predicate disambiguation batch_69cc5c21e64c81908490e3b0875dc0d6 completed March 31, 2026, 11:43 p.m.
PDg Predicate description generation batch_69cc5cff3608819081d2d7e5c16d44b7 completed March 31, 2026, 11:47 p.m.
Created at: March 30, 2026, 6:46 p.m.