Triple

T18819815
Position Surface form Disambiguated ID Type / Status
Subject Timberland E460234 entity
Predicate brandKnownFor P133541 FINISHED
Object rugged waterproof boots 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: rugged waterproof boots | Statement: [Timberland, brandKnownFor, rugged waterproof boots]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: brandKnownFor
Context triple: [Timberland, brandKnownFor, rugged waterproof boots]
  • A. creatorKnownFor
    Indicates that a creator is especially recognized or notable for a particular work, contribution, or achievement.
  • B. namedForKnownFor
    Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
  • C. segmentKnownFor
    Indicates that a specific segment or portion of something is recognized or notable for a particular characteristic, feature, or association.
  • D. formerlyKnownFor
    Indicates that an entity was previously recognized or notable for a particular role, attribute, or activity, but is no longer primarily associated with it.
  • E. alsoKnownFor
    Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
  • 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_69d8dcf94c288190a06dea029ae4b223 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5a6b9be988190b5e3804c39dc7dd9 completed April 20, 2026, 4:08 a.m.
PD Predicate disambiguation batch_69e48d1b10ec8190985c6fb5766ff981 completed April 19, 2026, 8:06 a.m.
PDg Predicate description generation batch_69e49a9bcc0c81908df3e513fd6762ff completed April 19, 2026, 9:04 a.m.
Created at: April 10, 2026, 11:55 a.m.