Triple
T7460527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince George’s County Charter |
E176233
|
entity |
| Predicate | enforcedWithin |
P15565
|
FINISHED |
| Object | territory of Prince George’s County, Maryland |
—
|
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: territory of Prince George’s County, Maryland | Statement: [Prince George’s County Charter, enforcedWithin, territory of Prince George’s County, Maryland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcedWithin Context triple: [Prince George’s County Charter, enforcedWithin, territory of Prince George’s County, Maryland]
-
A.
enforcedOn
Indicates that a rule, policy, or constraint is applied with authority to a particular target or subject.
-
B.
enforcedProvision
Indicates that an authority or agent compelled compliance with a specific rule, term, or provision.
-
C.
maintainedWithin
Indicates that one entity is kept, preserved, or sustained inside the boundaries or context of another entity.
-
D.
enforcedInRegion
chosen
Indicates that a rule, policy, or condition is actively applied and upheld within a specified geographic or administrative region.
-
E.
canEnforce
Indicates that one entity has the authority or capability to compel compliance with rules, decisions, or obligations upon another 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d525708190b7838e07ac2fbe1f |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:38 p.m.