Triple
T25916075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saugatuck River historic area |
E653039
|
entity |
| Predicate | hasPrimaryFunctionHistoric |
P88
|
FINISHED |
| Object | maritime commerce |
—
|
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: maritime commerce | Statement: [Saugatuck River historic area, hasPrimaryFunctionHistoric, maritime commerce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryFunctionHistoric Context triple: [Saugatuck River historic area, hasPrimaryFunctionHistoric, maritime commerce]
-
A.
hasPrimaryUseHistoric
Indicates that something is primarily used for historic or heritage-related purposes.
-
B.
hasPrimaryFunction
chosen
Indicates that one entity serves as the main or principal function or role of another entity.
-
C.
hasPlannedPrimaryFunction
Indicates that an entity is intended or designed to perform a specified main function or role.
-
D.
hasHistoricFeatures
Indicates that something possesses characteristics, elements, or attributes of historical significance.
-
E.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
- 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 22, 2026, 8:31 a.m.