Triple
T3608273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Fire of Rome |
E76424
|
entity |
| Predicate | popularRumor |
P28032
|
FINISHED |
| Object | Nero ordered the fire |
—
|
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: Nero ordered the fire | Statement: [Great Fire of Rome, popularRumor, Nero ordered the fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularRumor Context triple: [Great Fire of Rome, popularRumor, Nero ordered the fire]
-
A.
rumorContent
chosen
Indicates that the associated information specifies the subject matter or details contained within a particular rumor.
-
B.
popularFor
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
-
C.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
D.
popularName
Indicates that the object is a commonly used or widely recognized name or nickname for the subject.
-
E.
notableStory
Indicates that an entity is the subject or source of a story, account, or narrative that is considered notable or significant.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc22a3cf081908c20b6fb55be0db2 |
completed | March 8, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.