Triple
T406593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fratelli tutti |
E9394
|
entity |
| Predicate | mentionsEvent |
P831
|
FINISHED |
| Object | COVID-19 pandemic |
—
|
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: COVID-19 pandemic | Statement: [Fratelli tutti, mentionsEvent, COVID-19 pandemic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsEvent Context triple: [Fratelli tutti, mentionsEvent, COVID-19 pandemic]
-
A.
mentions
chosen
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
B.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
C.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
D.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
E.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbc00508190bbb602179273f29c |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e971a3a481909e6b075f25dd234a |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.