Triple
T29005903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudafjorden |
E736432
|
entity |
| Predicate | hasIndustrialActivityAtInnerEnd |
P113066
|
FINISHED |
| Object | Sauda |
—
|
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: Sauda | Statement: [Saudafjorden, hasIndustrialActivityAtInnerEnd, Sauda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndustrialActivityAtInnerEnd Context triple: [Saudafjorden, hasIndustrialActivityAtInnerEnd, Sauda]
-
A.
hasIndustrialSiteIn
chosen
Indicates that an entity possesses, operates, or is responsible for an industrial facility located within a specified place or area.
-
B.
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).
-
C.
connectsToIndustrialArea
Indicates that one entity has a direct link, route, or access connection to an industrial area.
-
D.
hasIndustrialAreaType
Indicates that an entity’s industrial area is classified as a specific type or category of industrial zone.
-
E.
containsIndustrialAreas
Indicates that one entity includes or encompasses industrial areas within its boundaries or scope.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: April 28, 2026, 9:37 a.m.