Triple
T16173601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Puy route |
E392503
|
entity |
| Predicate | seasonOfHighestUse |
P1166
|
FINISHED |
| Object | spring |
—
|
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: spring | Statement: [Le Puy route, seasonOfHighestUse, spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonOfHighestUse Context triple: [Le Puy route, seasonOfHighestUse, spring]
-
A.
peakSeasonMonth
Indicates the month or months during which something (such as demand, activity, or occurrence) reaches its highest or most intense level.
-
B.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
C.
seasonMonths
Indicates the set of calendar months during which a given season occurs.
-
D.
season
chosen
Indicates that an entity participates in, is associated with, or occurs during a particular season or seasonal period.
-
E.
peakSeasonReason
Indicates that there is a specific cause or justification for why a given time period is considered the peak season for something.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb9b8208190b60874cec7a3a98e |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.