Triple
T24080805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland |
E596497
|
entity |
| Predicate | hasFederalEnclave |
P154772
|
FINISHED |
| Object | Fort Meade |
—
|
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: Fort Meade | Statement: [Maryland, hasFederalEnclave, Fort Meade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFederalEnclave Context triple: [Maryland, hasFederalEnclave, Fort Meade]
-
A.
hasFederalCapitalWithin
Indicates that a country or federal entity has its official federal capital city located within the boundaries of a specified geographic area.
-
B.
locatedInFederalEntity
Indicates that one entity is geographically or administratively situated within the jurisdiction or boundaries of a specified federal entity.
-
C.
isPartOfFederalCity
Indicates that an entity is located within and administratively belongs to a designated federal city.
-
D.
includesFederalDistrict
Indicates that one administrative or geographic entity contains or encompasses a federal district within its boundaries.
-
E.
isWithinFederalCapitalTerritory
Indicates that one entity is geographically located inside the boundaries of the federal capital territory of another governing body or jurisdiction.
- F. None of above. chosen
Provenance (4 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc2351e08190857d57f266d1d4bf |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:43 p.m.