Triple
T35460213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-GAC |
E1024892
|
entity |
| Predicate | servesJurisdictionsType |
P152585
|
FINISHED |
| Object | counties |
—
|
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: counties | Statement: [H-GAC, servesJurisdictionsType, counties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesJurisdictionsType Context triple: [H-GAC, servesJurisdictionsType, counties]
-
A.
includesJurisdictionType
chosen
Indicates that a given entity’s authority, scope, or coverage extends to and encompasses a specified type of jurisdiction.
-
B.
jurisdictionIncludesService
Indicates that a particular jurisdiction encompasses or has authority over the specified service.
-
C.
usesJurisdictionType
Indicates that one entity applies, operates under, or is governed by a particular type or category of jurisdiction.
-
D.
typicalInJurisdictionType
Indicates that something is commonly or characteristically found, practiced, or applicable within a specified type of jurisdiction.
-
E.
definedJurisdictionOf
Indicates that one entity formally establishes or specifies the scope, boundaries, or authority of another entity’s jurisdiction.
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: May 3, 2026, 4:04 p.m.