Triple
T147992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Higher Education Area |
E3370
|
entity |
| Predicate | hasOutput |
P92
|
FINISHED |
| Object | communiqués of Bologna ministerial conferences |
—
|
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: communiqués of Bologna ministerial conferences | Statement: [European Higher Education Area, hasOutput, communiqués of Bologna ministerial conferences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutput Context triple: [European Higher Education Area, hasOutput, communiqués of Bologna ministerial conferences]
-
A.
hasOutputType
chosen
Indicates that an entity produces, returns, or yields a result of a specified type.
-
B.
hasCurrent
Indicates that an entity presently possesses, exhibits, or is associated with a particular state, attribute, or resource at the current time.
-
C.
hasProcess
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
D.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
E.
hasProduct
Indicates that an entity possesses, offers, or is associated with a particular product.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256580c2c8190beecca60ca8595f3 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.