Triple
T33908305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stettiner Vulcan AG |
E869245
|
entity |
| Predicate | operatedInPortCity |
P14306
|
FINISHED |
| Object | Stettin |
—
|
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: Stettin | Statement: [Stettiner Vulcan AG, operatedInPortCity, Stettin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInPortCity Context triple: [Stettiner Vulcan AG, operatedInPortCity, Stettin]
-
A.
hasPortCity
Indicates that a place or region possesses or is associated with a city that functions as its port.
-
B.
portCityInvolved
Indicates that a port city participates in, is affected by, or plays a role in a specified event, process, or relationship.
-
C.
isPortCityOn
Indicates that a city functions as a port located on the specified body of water.
-
D.
operatedLargestPortIn
Indicates that an entity operated the largest port located within a specified geographic or political region.
-
E.
notableCityOfOperation
chosen
Indicates that a city is a primary or particularly significant location where an entity conducts its operations or activities.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a009273634c8190b5b9c87053b56760 |
completed | May 10, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_6a0092171230819096e4274dd97e0410 |
completed | May 10, 2026, 2:11 p.m. |
Created at: May 1, 2026, 1:48 a.m.