Triple
T36127631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Werbellinsee |
E1044925
|
entity |
| Predicate | hasActivityInfrastructure |
P191842
|
FINISHED |
| Object | marinas |
—
|
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: marinas | Statement: [Werbellinsee, hasActivityInfrastructure, marinas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActivityInfrastructure Context triple: [Werbellinsee, hasActivityInfrastructure, marinas]
-
A.
hasAccessInfrastructure
Indicates that an entity is equipped with or connected to the physical or technical infrastructure necessary to access a particular service, resource, or network.
-
B.
hasInfrastructureAbove
Indicates that one entity’s infrastructure is physically located above or over another entity.
-
C.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
D.
hasGlobalInfrastructure
Indicates that an entity possesses infrastructure, facilities, or operational capabilities that are distributed across multiple countries or regions worldwide.
-
E.
hasActivityProvider
Indicates that an entity is the provider or organizer responsible for delivering a specified activity.
- F. None of above. chosen
Provenance (4 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: May 3, 2026, 4:08 p.m.