Triple
T21236416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spetses |
E523353
|
entity |
| Predicate | flagRaisedForRevolution |
P98547
|
FINISHED |
| Object | 3 April 1821 |
—
|
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: 3 April 1821 | Statement: [Spetses, flagRaisedForRevolution, 3 April 1821]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagRaisedForRevolution Context triple: [Spetses, flagRaisedForRevolution, 3 April 1821]
-
A.
flagFlown
Indicates that a particular flag is being displayed or flown at a specific location or by a specific entity.
-
B.
flag
Indicates that one entity marks, signals, or draws attention to another entity, often to denote status, importance, or the need for review or action.
-
C.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
D.
flagElement
Indicates that one entity serves as a flag or marker element associated with another entity, typically used to signal a condition, state, or special handling.
-
E.
flagRaisedDate
chosen
Indicates the date on which a particular flag was raised.
- 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735202c7481909c642ddaafb40671 |
completed | April 21, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:46 p.m.