Triple
T21391162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fabius, Alabama |
E527651
|
entity |
| Predicate | isSubjectToCountyRegulation |
P43654
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fabius, Alabama, isSubjectToCountyRegulation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubjectToCountyRegulation Context triple: [Fabius, Alabama, isSubjectToCountyRegulation, true]
-
A.
isSubjectToCountyGovernment
chosen
Indicates that an entity falls under the jurisdiction, authority, or administrative control of a county-level government.
-
B.
subjectToRegulation
Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
-
C.
isInCountyClass
Indicates that one entity (such as a place or institution) belongs to, or is categorized within, a particular county classification.
-
D.
isInCountySeatJurisdiction
Indicates that one entity falls under the legal or administrative authority of the county seat associated with another entity.
-
E.
isInCountySubdivision
Indicates that one entity (typically a place or address) is located within the boundaries of a specific county subdivision.
- 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b113690c81909c0a378fddba5d3a |
completed | April 22, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:13 p.m.