Triple
T6568420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hickling Broad |
E153970
|
entity |
| Predicate | eraOfFormation |
P48685
|
FINISHED |
| Object | medieval period |
—
|
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: medieval period | Statement: [Hickling Broad, eraOfFormation, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfFormation Context triple: [Hickling Broad, eraOfFormation, medieval period]
-
A.
eraOfEstablishment
chosen
Indicates the time period or historical era during which an entity was founded or established.
-
B.
historicalFormation
Indicates the process or circumstances through which something came into existence or took shape over time in history.
-
C.
countryFormed
Indicates that one country was created, established, or came into existence as a result of another country or political entity.
-
D.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
-
E.
foundingAround
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:53 p.m.