Triple
T28686866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Beach, Florida |
E729157
|
entity |
| Predicate | hasGovernmentService |
P150630
|
FINISHED |
| Object | municipal government |
—
|
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: municipal government | Statement: [Golden Beach, Florida, hasGovernmentService, municipal government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernmentService Context triple: [Golden Beach, Florida, hasGovernmentService, municipal government]
-
A.
hasGovernmentServicesProvidedBy
chosen
Indicates that one entity receives its governmental services from, or is administratively served by, another entity.
-
B.
governmentBodyServed
Indicates that one entity has served in an official capacity within, or as a member of, a particular government body.
-
C.
governmentBranchServed
Indicates that an entity has served in or been a member of a particular branch of government.
-
D.
federalService
Indicates that an entity is engaged in or associated with work, duties, or service under the authority of a federal government.
-
E.
governmentServed
Indicates that a person has held a position serving in or working for a particular government.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 5:33 a.m.