Triple
T25154956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMS |
E626283
|
entity |
| Predicate | administrativeSeatOfDistrict |
P159058
|
FINISHED |
| Object | Nassau |
—
|
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: Nassau | Statement: [EMS, administrativeSeatOfDistrict, Nassau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeSeatOfDistrict Context triple: [EMS, administrativeSeatOfDistrict, Nassau]
-
A.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
B.
adminDistrictSeat
chosen
Indicates that one entity serves as the administrative center or capital seat of an administrative district to which the other entity belongs.
-
C.
governmentalDistrictOf
Indicates that a governmental district is the administrative district to which a given entity belongs or in which it is located.
-
D.
seatOfCountyAdministrativeBoard
Indicates that a location serves as the official seat or headquarters of a county-level administrative board.
-
E.
administrativeCouncilArea
Indicates that one entity is an administrative council area within which the other entity is located or governed.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 6:30 a.m.