Triple
T30414123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huangpu River cruises |
E773704
|
entity |
| Predicate | notableAreaViewed |
P207270
|
FINISHED |
| Object | the Bund |
E38100
|
NE 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: the Bund | Statement: [Huangpu River cruises, notableAreaViewed, the Bund]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAreaViewed Context triple: [Huangpu River cruises, notableAreaViewed, the Bund]
-
A.
notableDisplay
Indicates that something is prominently or distinctively presented in a way that draws special attention or recognition.
-
B.
notableScreening
Indicates that an entity had a particularly significant or noteworthy screening or showing of a work (such as a film or performance).
-
C.
notablePresence
Indicates that an entity has a significant or prominent presence in relation to another entity, context, or domain.
-
D.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
-
E.
notableExposure
Indicates that an entity has received significant public attention, visibility, or coverage, making it notably exposed or recognized.
- F. None of above. chosen
Provenance (5 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27895fdda08190821d66cfceccb6f6 |
completed | June 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 8:05 p.m.