Triple

T17322153
Position Surface form Disambiguated ID Type / Status
Subject Commissioner to the United States for the Republic of Texas E420586 entity
Predicate timeframeApproximateStart P48368 FINISHED
Object early 1830s 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: early 1830s | Statement: [Commissioner to the United States for the Republic of Texas, timeframeApproximateStart, early 1830s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeframeApproximateStart
Context triple: [Commissioner to the United States for the Republic of Texas, timeframeApproximateStart, early 1830s]
  • A. timeframeApproximate
    Indicates that the time period associated with an event or relation is not exact but only roughly or loosely specified.
  • B. timeStartApprox chosen
    Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
  • C. endTimeApproximate
    Indicates that the recorded end time of an event or action is not exact but an approximate value.
  • D. estimatedStartDate
    Indicates the date on which something is expected or planned to begin, based on current information or projections.
  • E. timePeriodEndApprox
    Indicates that the associated time period ends at an approximate, rather than exact, point in time.
  • 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_69d889d22b848190a4663d0b8f8f76e7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e439d01e2c8190a358dace420d4575 completed April 19, 2026, 2:11 a.m.
PD Predicate disambiguation batch_69e3b01b9d1c8190a406dd941c9b11a1 completed April 18, 2026, 4:23 p.m.
Created at: April 10, 2026, 5:43 a.m.