Triple
T4053177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historic county of Middlesex |
E84631
|
entity |
| Predicate | currentCeremonialUseOfName |
P53025
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [historic county of Middlesex, currentCeremonialUseOfName, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentCeremonialUseOfName Context triple: [historic county of Middlesex, currentCeremonialUseOfName, limited]
-
A.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
-
B.
ceremonialOrigin
Indicates that something originates from, or is derived through, a formal ceremony or ritual practice.
-
C.
currentOfficialNameSince
Indicates the date or time from which an entity has borne its current official name.
-
D.
isCeremonial
Indicates that something is associated with, intended for, or used in a formal ceremony or ritual rather than for ordinary or practical purposes.
-
E.
currentName
Indicates the present or most recently assigned name associated with an entity.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef9fcb31c819098d5287b6fc84f4e |
completed | March 9, 2026, 4:49 p.m. |
Created at: March 9, 2026, 3:37 p.m.