Triple
T9315461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ennis, Texas |
E224105
|
entity |
| Predicate | legislativeTitle |
P88046
|
FINISHED |
| Object | Official Bluebonnet City of Texas |
—
|
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: Official Bluebonnet City of Texas | Statement: [Ennis, Texas, legislativeTitle, Official Bluebonnet City of Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeTitle Context triple: [Ennis, Texas, legislativeTitle, Official Bluebonnet City of Texas]
-
A.
headOfLegislatureTitle
Indicates the official title held by the person who serves as the head of a legislature.
-
B.
legislativeArticle
Indicates a relationship where one entity is a specific article or clause within a legislative or legal document that governs or regulates another entity.
-
C.
typeOfLegislation
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
-
D.
signedLegislation
Indicates that an authority formally approved and enacted a piece of legislation into law by signing it.
-
E.
legislature
Indicates that an entity serves as, or is part of, a law-making body or assembly responsible for creating or amending laws for a political unit.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd358846e48190a8aacfab19d88ae7 |
completed | April 1, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:37 p.m.