Triple
T12298490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wuse Market |
E293151
|
entity |
| Predicate | typicalPeakPeriod |
P6833
|
FINISHED |
| Object | festive seasons |
—
|
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: festive seasons | Statement: [Wuse Market, typicalPeakPeriod, festive seasons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPeakPeriod Context triple: [Wuse Market, typicalPeakPeriod, festive seasons]
-
A.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
B.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
C.
typicalTimes
chosen
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
D.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
-
E.
peakDay
Indicates the specific day on which a quantity, activity, or effect reaches its maximum level within a given 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69dadcd4cb008190af99c4856e76ac08 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:52 p.m.