Triple
T7141070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee trial court system |
E166439
|
entity |
| Predicate | numberOfJudicialDistricts |
P1679
|
FINISHED |
| Object | 31 |
—
|
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: 31 | Statement: [Tennessee trial court system, numberOfJudicialDistricts, 31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfJudicialDistricts Context triple: [Tennessee trial court system, numberOfJudicialDistricts, 31]
-
A.
numberOfDistricts
chosen
Indicates the total count of districts associated with a given entity or area.
-
B.
numberOfJurisdictions
Indicates the count of distinct legal or administrative jurisdictions associated with or applicable to an entity or situation.
-
C.
hasJudicialDistrict
Indicates that an entity falls within or is associated with a specific judicial district for legal or court-related purposes.
-
D.
numberOfCourts
Indicates the quantity of courts associated with or present at a given entity or location.
-
E.
judicialCircuit
Indicates the judicial circuit within which a legal entity, case, or jurisdiction is organized or falls under authority.
- 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e778875c8190a5202d3efe5a842d |
completed | March 27, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.