Triple

T22970357
Position Surface form Disambiguated ID Type / Status
Subject Taylor E571169 entity
Predicate historicallyIndicates P150444 FINISHED
Object ancestor worked as a tailor 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: ancestor worked as a tailor | Statement: [Taylor, historicallyIndicates, ancestor worked as a tailor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyIndicates
Context triple: [Taylor, historicallyIndicates, ancestor worked as a tailor]
  • A. historicallyIn
    Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
  • B. historicallyGivenIn
    Indicates that something was customarily or traditionally granted, presented, or assigned to something or someone in the past.
  • C. historicallyEncompassed
    Indicates that one entity previously included, covered, or contained another entity within its scope, extent, or boundaries during a past historical period.
  • D. historicallyConsidered
    Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
  • E. historicallyLinked
    Indicates that two entities are connected through a shared or related historical event, period, or development.
  • 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_69e245b2c6548190a0e4c7f2f7df2d48 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1823272c4819083e4653d231facec completed April 29, 2026, 3:59 a.m.
PD Predicate disambiguation batch_69ef3b9101f48190a06c69dff26c6441 completed April 27, 2026, 10:33 a.m.
PDg Predicate description generation batch_69ef538a115081908982597f79355840 completed April 27, 2026, 12:16 p.m.
Created at: April 17, 2026, 3:48 p.m.