Triple
T16658778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiangshan Hiking Trail |
E404802
|
entity |
| Predicate | peakCrowdTimes |
P57188
|
FINISHED |
| Object | sunset |
—
|
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: sunset | Statement: [Xiangshan Hiking Trail, peakCrowdTimes, sunset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakCrowdTimes Context triple: [Xiangshan Hiking Trail, peakCrowdTimes, sunset]
-
A.
peakActivity
Indicates that an entity is at its highest or most intense level of activity within a given period or context.
-
B.
timeSlotOfWorks
Indicates the specific time period or interval during which the works (e.g., tasks, events, or activities) are scheduled or take place.
-
C.
peakServicePeriod
Indicates the time interval during which a service experiences its highest or most intensive level of use or operation.
-
D.
peakHours
chosen
Indicates that an action, event, or condition occurs during the busiest or most heavily trafficked time period.
-
E.
peakDays
Indicates the days on which something reaches its highest or most intense level of activity, usage, or occurrence.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bfcbb6881909c0419174dd017dc |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.