Triple
T5332618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prora complex |
E123344
|
entity |
| Predicate | intendedCapacity |
P28148
|
FINISHED |
| Object | 20000 holidaymakers |
—
|
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: 20000 holidaymakers | Statement: [Prora complex, intendedCapacity, 20000 holidaymakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedCapacity Context triple: [Prora complex, intendedCapacity, 20000 holidaymakers]
-
A.
originalCapacity
chosen
Indicates the initial or designed maximum amount or volume that something can hold, process, or produce before any changes or adjustments.
-
B.
currentCapacity
Indicates the present amount of capacity an entity is using or able to provide at a given time.
-
C.
laterCapacity
Indicates that one entity’s capacity or capability occurs, becomes available, or is realized at a later time than another’s.
-
D.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
E.
approximateCapacity
Indicates that one entity has an estimated or rough capacity value relative to another or to a specified measure.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ac8e10819088b6a9e02d927044 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.