Triple
T16786592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horncastle |
E407994
|
entity |
| Predicate | hasCattleMarketHistory |
P17485
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Horncastle, hasCattleMarketHistory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCattleMarketHistory Context triple: [Horncastle, hasCattleMarketHistory, yes]
-
A.
hasHistoricMarket
Indicates that an entity possesses or is the location of a market of historical significance.
-
B.
hasMarketTownHistory
chosen
Indicates that an entity has a historical association with functioning as a market town or possessing recognized market-town status in the past.
-
C.
hasMarketCommodity
Indicates that an entity is associated with or trades in a particular commodity within a market context.
-
D.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
E.
hasMarketData
Indicates that an entity possesses or is associated with relevant market-related information or statistics.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21a52ac8190b4374aa0fc45683a |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.