Triple
T31157059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's County |
E794237
|
entity |
| Predicate | historicalBaroniesIncluded |
P154320
|
FINISHED |
| Object | Maryborough East |
—
|
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: Maryborough East | Statement: [Queen's County, historicalBaroniesIncluded, Maryborough East]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalBaroniesIncluded Context triple: [Queen's County, historicalBaroniesIncluded, Maryborough East]
-
A.
isAmongOldestBaronies
Indicates that the barony is one of the earliest-established or longest-standing baronies within a given set or region.
-
B.
historicBarony
Indicates that an entity has the status or role of a historic barony, i.e., it was once recognized as a baronial territorial or feudal jurisdiction.
-
C.
locatedInHistoricBarony
chosen
Indicates that one entity is situated within the geographical area of a historically recognized barony.
-
D.
hasBarony
Indicates that one entity possesses or is assigned authority over a barony associated with another entity.
-
E.
hasHistoricHamlets
Indicates that an entity possesses or is associated with one or more historically recognized hamlets.
- 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: April 29, 2026, 9:07 p.m.