Triple
T29293527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miluo River |
E742749
|
entity |
| Predicate | hasNotablePlaceOnBank |
P153329
|
FINISHED |
| Object | Miluo City Dragon Boat Festival sites |
—
|
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: Miluo City Dragon Boat Festival sites | Statement: [Miluo River, hasNotablePlaceOnBank, Miluo City Dragon Boat Festival sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePlaceOnBank Context triple: [Miluo River, hasNotablePlaceOnBank, Miluo City Dragon Boat Festival sites]
-
A.
hasLandmarkOnBank
Indicates that a landmark is located on the bank (shore or edge) of a geographic feature such as a river, lake, or canal.
-
B.
hasCityOnBank
Indicates that a city is located on the bank of a particular river or body of water.
-
C.
hasProvinceOnBank
Indicates that a province is located along or adjacent to the bank of a specified body of water.
-
D.
hasBankOn
Indicates that one entity is located on or alongside the bank (edge) of another entity, typically a river, lake, or similar body.
-
E.
containsNotablePlace
chosen
Indicates that one location includes within its boundaries a place that is considered notable or significant.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
Created at: April 28, 2026, 1:04 p.m.