Triple
T33571939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurobe Dam |
E859922
|
entity |
| Predicate | constructionWorkers |
P14451
|
FINISHED |
| Object | thousands |
—
|
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: thousands | Statement: [Kurobe Dam, constructionWorkers, thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionWorkers Context triple: [Kurobe Dam, constructionWorkers, thousands]
-
A.
constructionLabor
chosen
Indicates a relationship where an entity performs or provides labor specifically for construction-related work or projects.
-
B.
constructionSite
Indicates that an entity is a location or area where construction work is actively taking place or is planned to occur.
-
C.
constructionAssociatedWith
Indicates a relationship where a construction (such as a building, structure, or construction activity) is linked or related to another entity, context, or process.
-
D.
constructionExpanded
Indicates that a construction project or structure has been enlarged or extended beyond its original size or scope.
-
E.
constructionCompany
Indicates a relationship where an entity functions as a company engaged in construction-related activities or services for another entity or project.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 1, 2026, 1:40 a.m.