Triple
T30155440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 长江 |
E766507
|
entity |
| Predicate | 重要工程 |
P7519
|
FINISHED |
| Object | 三峡工程 |
—
|
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: 三峡工程 | Statement: [长江, 重要工程, 三峡工程]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 重要工程 Context triple: [长江, 重要工程, 三峡工程]
-
A.
majorConstructionUnder
Indicates that a location or structure is currently undergoing significant construction work or large-scale building activity.
-
B.
majorConstruction
Indicates a relationship where a construction project is large-scale, significant, or of primary importance in scope, impact, or resources.
-
C.
significantInfrastructure
chosen
Indicates that an entity constitutes an important or critical piece of infrastructure within a system, network, or region.
-
D.
isMajorInfrastructure
Indicates that the entity functions as a primary, large-scale facility or system essential to the operation of a region’s or organization’s core services or networks.
-
E.
includesMajorInfrastructure
Indicates that the subject area or entity contains significant, large-scale infrastructure elements essential for core operations or services.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed72fb08190955d6bfd90dd3b8e |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:20 p.m.