Triple
T26405898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanguan Ancient Town |
E663830
|
entity |
| Predicate | bestKnownEvent |
P160509
|
FINISHED |
| Object | Qiantang River tidal bore viewing |
—
|
NE NERFINISHED |
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: Qiantang River tidal bore viewing | Statement: [Yanguan Ancient Town, bestKnownEvent, Qiantang River tidal bore viewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestKnownEvent Context triple: [Yanguan Ancient Town, bestKnownEvent, Qiantang River tidal bore viewing]
-
A.
lastMajorEvent
Indicates the most recent significant event associated with an entity in a given context.
-
B.
bearerNotableEvent
Indicates that a bearer (such as a person or entity) is associated with a specific notable event in which they played a significant role.
-
C.
youngestEvent
Indicates that the referenced event is the most recent or last-occurring event among a set of events.
-
D.
lastRecordedEvent
Indicates the most recent event that has been recorded for a given entity or context.
-
E.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610f87374819084279ca5c2f3d32f |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:35 p.m.