Triple

T4555128
Position Surface form Disambiguated ID Type / Status
Subject PHP License E120461 entity
Predicate requiresNamePreservation P52923 FINISHED
Object true 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: true | Statement: [PHP License, requiresNamePreservation, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresNamePreservation
Context triple: [PHP License, requiresNamePreservation, true]
  • A. preservesFeature
    Indicates that one entity maintains or keeps intact a particular feature, property, or characteristic of another entity during some process or interaction.
  • B. preservesFragmentsOf
    Indicates that one entity maintains, protects, or keeps intact partial remains or pieces of another entity.
  • C. preservesLanguage
    Indicates that an entity actively maintains, protects, or continues the use of a particular language so it does not decline or disappear.
  • D. mustRetain chosen
    Indicates that an entity is required to keep or preserve another entity and is not allowed to discard, delete, or release it.
  • E. preservesOwnHierarchy
    Indicates that an entity maintains and does not alter the structural hierarchy of its own internal components or organization.
  • 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_69bd4636f1648190a701445c2fcd9c17 completed March 20, 2026, 1:05 p.m.
NER Named-entity recognition batch_69bd5813af948190b10b02dadf6496bf completed March 20, 2026, 2:22 p.m.
PD Predicate disambiguation batch_69bd5223423c81908317351b58cff5f5 completed March 20, 2026, 1:56 p.m.
Created at: March 20, 2026, 1:09 p.m.