Triple

T28337305
Position Surface form Disambiguated ID Type / Status
Subject Georgia Byrd E717710 entity
Predicate transformsFrom P56260 FINISHED
Object timid employee 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: timid employee | Statement: [Georgia Byrd, transformsFrom, timid employee]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transformsFrom
Context triple: [Georgia Byrd, transformsFrom, timid employee]
  • A. transformsUnder
    Indicates a relationship where one entity changes form, state, or structure when subjected to the influence, conditions, or operation specified by another entity.
  • B. transformType chosen
    Indicates that one entity is converted or changed from its original form into another specified type or form.
  • C. transformedIn
    Indicates that one entity has been changed, converted, or altered into another state, form, or representation within a specific context or process.
  • D. inverseTransform
    Indicates that one entity represents the inverse operation or mapping that undoes the transformation performed by another entity.
  • E. coordinateTransformation
    Indicates a relationship where one coordinate system is mathematically converted or mapped into another, preserving the correspondence of points between them.
  • 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_69eff6e9a57c8190a69c2c74b5d72119 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69fbc9d1dba881908c399b8e1dc13ce2 completed May 6, 2026, 11:08 p.m.
PD Predicate disambiguation batch_69fbc8ec03ac8190a757563f96fab283 completed May 6, 2026, 11:04 p.m.
Created at: April 28, 2026, 12:37 a.m.