Triple
T31809729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Enterprise Zone Program |
E811969
|
entity |
| Predicate | designationDuration |
P540
|
FINISHED |
| Object | up to five years |
—
|
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: up to five years | Statement: [Texas Enterprise Zone Program, designationDuration, up to five years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designationDuration Context triple: [Texas Enterprise Zone Program, designationDuration, up to five years]
-
A.
occupationDuration
Indicates the length of time an entity holds or has held a particular occupation or role.
-
B.
denotesTenure
Indicates that one entity holds or has held a position, role, or office at another entity for a specified period of time.
-
C.
termLengthCharacteristic
Indicates the specific duration-related property or feature associated with a term (such as its length or time span).
-
D.
termLength
chosen
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
E.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 30, 2026, 11:43 p.m.