Triple
T18557269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Government of Nashville and Davidson County |
E453536
|
entity |
| Predicate | hasNumberOfCouncilMembers |
P2433
|
FINISHED |
| Object | 40 |
—
|
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: 40 | Statement: [Metropolitan Government of Nashville and Davidson County, hasNumberOfCouncilMembers, 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfCouncilMembers Context triple: [Metropolitan Government of Nashville and Davidson County, hasNumberOfCouncilMembers, 40]
-
A.
hasNumberOfCouncillors
chosen
Indicates the relationship that specifies how many councillors are associated with a given entity.
-
B.
hasCouncillors
Indicates that an entity is associated with one or more councillors who serve or represent it in an official capacity.
-
C.
hasNumberOfMPs
Indicates the relationship that specifies how many members of parliament (MPs) are associated with a given entity.
-
D.
hasNumberOfDeputies
Indicates the specific count of deputies associated with or assigned to an entity.
-
E.
numberOfDistrictMembers
Indicates the relationship that specifies how many members are associated with a given district.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53808028c8190825630525d84a29b |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:40 a.m.