Triple
T23935655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appleby Horse Fair |
E602626
|
entity |
| Predicate | hasApproximateOrigins |
P82776
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Appleby Horse Fair, hasApproximateOrigins, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateOrigins Context triple: [Appleby Horse Fair, hasApproximateOrigins, 17th century]
-
A.
hasApproximateOrigin
chosen
Indicates that an entity originates from a source or location that is known only approximately rather than precisely.
-
B.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
hasLikelyOrigin
Indicates that one entity is inferred or believed, with some degree of uncertainty, to be the source or starting point of another entity.
-
D.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
E.
hasEstimatedOriginalVolume
Indicates that an entity is associated with an approximate or calculated value for its original volume.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cf9e8abc8190a3028a358265912e |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:02 p.m.