Triple

T35374762
Position Surface form Disambiguated ID Type / Status
Subject Shoemaker (namesake unknown) E1021874 entity
Predicate likelySignificance P183558 FINISHED
Object local significance 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: local significance | Statement: [Shoemaker (namesake unknown), likelySignificance, local significance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: likelySignificance
Context triple: [Shoemaker (namesake unknown), likelySignificance, local significance]
  • A. likelyStatus
    Indicates the probable or expected state or condition of an entity based on available information or inference.
  • B. likelyIndicates
    Indicates that one fact, observation, or condition serves as probabilistic evidence suggesting, but not guaranteeing, the presence or truth of another.
  • C. likelyNotability
    Indicates that an entity is assessed as probably not meeting a specified threshold of importance, prominence, or significance within a given context.
  • D. likelyUse
    Indicates that one entity is expected or probable to use, employ, or make use of another entity in a given context.
  • E. likelyBehavior
    Indicates the behavior or action that an entity is expected or predicted to exhibit under given circumstances.
  • 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_69f76df000488190ab7c97f565677055 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7a01efcc08190bba489a9099b8684 completed May 3, 2026, 7:21 p.m.
PD Predicate disambiguation batch_69f79e4888248190be2f63cdfb5cd7b7 completed May 3, 2026, 7:13 p.m.
PDg Predicate description generation batch_69f79f477c4c8190a35cb6d87b1dcbd1 completed May 3, 2026, 7:17 p.m.
Created at: May 3, 2026, 4:03 p.m.