Triple
T26879509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jari River |
E676850
|
entity |
| Predicate | hasNearbyIndustrialProject |
P69562
|
FINISHED |
| Object | Jari Project |
—
|
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: Jari Project | Statement: [Jari River, hasNearbyIndustrialProject, Jari Project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyIndustrialProject Context triple: [Jari River, hasNearbyIndustrialProject, Jari Project]
-
A.
hasNearbyProject
chosen
Indicates that one entity has a project located within a close or specified proximity to another entity or reference point.
-
B.
hasNearbyIndustry
Indicates that an entity is located close to one or more industrial facilities or activities.
-
C.
hasNearbyProductionArea
Indicates that one entity has a production area located in close physical proximity to it.
-
D.
hasIndustrialSiteIn
Indicates that an entity possesses, operates, or is responsible for an industrial facility located within a specified place or area.
-
E.
hasIndustrialZoneAlong
Indicates that an industrial zone is located adjacent to or extending along the length of a specified linear feature (such as a road, river, or boundary).
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 27, 2026, 5:38 a.m.