Triple
T7697287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Comptroller of Public Accounts |
E174400
|
entity |
| Predicate | providedContent |
P17306
|
FINISHED |
| Object | Biennial Revenue Estimate |
—
|
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: Biennial Revenue Estimate | Statement: [Texas Comptroller of Public Accounts, providedContent, Biennial Revenue Estimate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedContent Context triple: [Texas Comptroller of Public Accounts, providedContent, Biennial Revenue Estimate]
-
A.
providedInformationTo
Indicates that one entity has supplied or communicated information to another entity.
-
B.
contentProvider
chosen
Indicates that one entity serves as the source or supplier of content (such as media, information, or data) for another entity.
-
C.
primaryContent
Indicates that one entity serves as the main or most important content associated with another entity.
-
D.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
E.
curatesContentFrom
Indicates that one entity selects, organizes, and presents content that originates from another entity.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.