Triple
T32915404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutsche Digitale Bibliothek |
E841995
|
entity |
| Predicate | aggregatesInto |
P125335
|
FINISHED |
| Object | Europeana |
—
|
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: Europeana | Statement: [Deutsche Digitale Bibliothek, aggregatesInto, Europeana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggregatesInto Context triple: [Deutsche Digitale Bibliothek, aggregatesInto, Europeana]
-
A.
groupedInto
Indicates that multiple entities are collected or organized together as members of a common group or category.
-
B.
supportsAggregation
Indicates that one entity enables or allows another entity to be combined, grouped, or summarized with others through an aggregation operation.
-
C.
organizesInto
Indicates that one entity arranges, structures, or groups another entity into a particular order, system, or set of categories.
-
D.
nestAggregation
chosen
Indicates that one aggregation is hierarchically contained within or grouped under another aggregation.
-
E.
aggregationProperty
Indicates that one entity serves as an aggregation or summary of values or instances associated with 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:19 a.m.