Triple
T333231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas's 15th congressional district |
E6668
|
entity |
| Predicate | representedSince |
P12504
|
FINISHED |
| Object | 1903 |
—
|
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: 1903 | Statement: [Texas's 15th congressional district, representedSince, 1903]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedSince Context triple: [Texas's 15th congressional district, representedSince, 1903]
-
A.
knownSince
Indicates the point in time from which one entity has been aware of, acquainted with, or in possession of knowledge about another entity.
-
B.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
C.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
-
D.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
E.
historicallyRecordedSince
Indicates that the existence, occurrence, or recognition of one entity has been documented in historical records starting from the time specified by another entity.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac4d9d081908a624464e450fb0e |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94d99cc8190a112e4b630ec63c1 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea7d03a88190aab72e61d8673488 |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.