Triple
T32497731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South–North Water Transfer Project |
E830572
|
entity |
| Predicate | notableBeneficiaryCity |
P93062
|
FINISHED |
| Object | Beijing |
E2312
|
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: Beijing | Statement: [South–North Water Transfer Project, notableBeneficiaryCity, Beijing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBeneficiaryCity Context triple: [South–North Water Transfer Project, notableBeneficiaryCity, Beijing]
-
A.
beneficiaryCity
chosen
Indicates that a city is the recipient or beneficiary of some action, service, resource, or arrangement.
-
B.
notableTerminusCity
Indicates that a city is notably recognized as a terminus (endpoint) of a route, line, or network.
-
C.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
D.
notableCityIncluded
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
-
E.
notableCitiesRepresented
Indicates that an entity includes or features certain cities as particularly important or prominently represented within it.
- F. None of above.
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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a347b70d8a0819097a2b63d6a786275 |
completed | June 18, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:59 a.m.