Triple
T1937156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Worldwide Developers Conference 2020 |
E41467
|
entity |
| Predicate | reasonForVirtualFormat |
P33719
|
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: [Apple Worldwide Developers Conference 2020, reasonForVirtualFormat, COVID-19 pandemic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForVirtualFormat Context triple: [Apple Worldwide Developers Conference 2020, reasonForVirtualFormat, COVID-19 pandemic]
-
A.
reasonForFolding
Indicates the cause or justification for an entity being folded, discontinued, or terminated.
-
B.
exactValueReason
Indicates that the value is specified exactly as given due to a particular justification or rationale.
-
C.
reasonForSplit
Indicates the cause, motivation, or circumstance that led to a separation or breakup between entities.
-
D.
reasonForMintLocation
Indicates that the specified location is the place where something (typically currency or tokens) is created or issued.
-
E.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2c752fc81909baf38ff1cdeb18c |
completed | March 7, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb25ef0ec8190b907963e9db0fe04 |
completed | March 7, 2026, 5:06 a.m. |
Created at: March 4, 2026, 7:36 p.m.