Triple

T34950070
Position Surface form Disambiguated ID Type / Status
Subject C. E. "Red" Reed E1007966 entity
Predicate legacyRecognizedAt P182115 FINISHED
Object Texas A&M University NE NERFINISHED

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: Texas A&M University | Statement: [C. E. "Red" Reed, legacyRecognizedAt, Texas A&M University]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legacyRecognizedAt
Context triple: [C. E. "Red" Reed, legacyRecognizedAt, Texas A&M University]
  • A. recognizedSince
    Indicates that one entity has formally acknowledged, accepted, or identified another entity as valid or legitimate starting from a specific point in time.
  • B. recognitionDate
    Indicates the date on which an entity, status, or achievement is formally acknowledged or officially recognized.
  • C. wasRecognizedAs
    Indicates that an entity was formally identified, acknowledged, or designated as having a particular role, status, or quality.
  • D. perpetuationRecognizedBy
    Indicates that the ongoing continuation or maintenance of something is formally acknowledged or validated by a particular entity or authority.
  • E. areRecognizedBy
    Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
  • 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_69f76dc5d4308190b77553ee07b1ede6 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78710282c81909146dc0be91e983f completed May 3, 2026, 5:34 p.m.
PD Predicate disambiguation batch_69f784162134819098413482ef52042f completed May 3, 2026, 5:21 p.m.
PDg Predicate description generation batch_69f7870dfe108190996c0c68630edc7f completed May 3, 2026, 5:34 p.m.
Created at: May 3, 2026, 4 p.m.