Triple
T19495821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Jacksonville, Florida |
E487766
|
entity |
| Predicate | cityCouncilMembers |
P87204
|
FINISHED |
| Object | 19 |
—
|
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: 19 | Statement: [Government of Jacksonville, Florida, cityCouncilMembers, 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityCouncilMembers Context triple: [Government of Jacksonville, Florida, cityCouncilMembers, 19]
-
A.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city council.
-
B.
council
Indicates that an entity serves as a governing or advisory council for another entity or within a particular domain.
-
C.
hasCouncillors
chosen
Indicates that an entity is associated with one or more councillors who serve or represent it in an official capacity.
-
D.
municipalRepresentation
Indicates that one entity serves as the official municipal-level representative or governing body for another entity within a specific locality or jurisdiction.
-
E.
cityCouncilRegion
Indicates the administrative region or jurisdiction that a particular city council governs or represents.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6349182ec81908dd301f802530eec |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.