Triple
T15223333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Ship Building Company |
E363814
|
entity |
| Predicate | vesselOperatingArea |
P6297
|
FINISHED |
| Object | inland seas |
—
|
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: inland seas | Statement: [American Ship Building Company, vesselOperatingArea, inland seas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vesselOperatingArea Context triple: [American Ship Building Company, vesselOperatingArea, inland seas]
-
A.
appliesToSeaArea
chosen
Indicates that something (such as a rule, restriction, or designation) is relevant or valid within a specified sea area.
-
B.
operatesVessel
Indicates that an agent is responsible for controlling, managing, or running the operation of a vessel.
-
C.
usesVesselsOperatedBy
Indicates that one entity makes use of vessels that are operated or controlled by another entity.
-
D.
marineAreaShare
Indicates the proportion of a larger marine area that is occupied, controlled, or otherwise attributed to a specific entity.
-
E.
seaAreaDesignation
Indicates the specific legal or administrative sea area classification that has been assigned to a given marine region.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078a9318819081db3b7bcc28e04f |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.