Triple
T35148388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oak Glen |
E1014914
|
entity |
| Predicate | servedByCountyGovernment |
P43654
|
FINISHED |
| Object | Monmouth County government |
—
|
NE NERFINISHED |
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: Monmouth County government | Statement: [Oak Glen, servedByCountyGovernment, Monmouth County government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByCountyGovernment Context triple: [Oak Glen, servedByCountyGovernment, Monmouth County government]
-
A.
servesCountyTown
Indicates that an entity (such as a service, office, or facility) provides coverage or service to a specified county or town.
-
B.
isSubjectToCountyGovernment
chosen
Indicates that an entity falls under the jurisdiction, authority, or administrative control of a county-level government.
-
C.
servesCountySeat
Indicates that one entity functions as the county seat (administrative center) for the specified county.
-
D.
servesTownship
Indicates that an entity provides official services or administrative functions to a particular township.
-
E.
countyGovernment
Indicates that a county-level governmental authority has jurisdiction over, administers, or is responsible for the referenced entity.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
Created at: May 3, 2026, 4:02 p.m.