Triple

T9841880
Position Surface form Disambiguated ID Type / Status
Subject Newport Lights E239246 entity
Predicate hasStrengthDescriptor P90286 FINISHED
Object light 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: light | Statement: [Newport Lights, hasStrengthDescriptor, light]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStrengthDescriptor
Context triple: [Newport Lights, hasStrengthDescriptor, light]
  • A. hasForceStrength
    Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
  • B. hasNotableStrengthIn
    Indicates that an entity possesses a particularly high level of ability, effectiveness, or advantage in a specific area or domain.
  • C. hasStrongField
    Indicates that one entity possesses or exhibits a powerful or intense field (such as a physical, electromagnetic, or influence field) relative to some context or standard.
  • D. estimatedStrength
    Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
  • E. hasDefenderStrength
    Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
  • 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_69ca84e3f0c48190ada72a65ebd50efd completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb34e3420819084bb31170e643cd0 completed April 2, 2026, 12:07 a.m.
PD Predicate disambiguation batch_69cd03e57cac8190914bb5ae608a6e0e completed April 1, 2026, 11:39 a.m.
PDg Predicate description generation batch_69cd06ace53081909b5f81f382f6591e completed April 1, 2026, 11:51 a.m.
Created at: March 30, 2026, 8:33 p.m.