Triple
T17630586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Market Place, Hitchin |
E429964
|
entity |
| Predicate | hasRegularEventType |
P128337
|
FINISHED |
| Object | street market |
—
|
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: street market | Statement: [Market Place, Hitchin, hasRegularEventType, street market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegularEventType Context triple: [Market Place, Hitchin, hasRegularEventType, street market]
-
A.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
B.
refersToEventType
Indicates that one entity references or is associated with a specific type or category of event.
-
C.
hasScheduleType
Indicates that an entity is associated with a particular kind or category of schedule (e.g., recurring, one-time, or specific scheduling pattern).
-
D.
appearsAtEventType
Indicates that an entity is present or participates in an event of a specified type.
-
E.
hasRegularServicePattern
Indicates that an entity consistently follows a defined, recurring schedule or pattern of service over time.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dc01b1c819099e3329cfb8cb77f |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 5:52 a.m.