Triple
T15454650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sansculottides |
E371737
|
entity |
| Predicate | themeOfLeapDay |
P118872
|
FINISHED |
| Object | revolution |
—
|
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: revolution | Statement: [Sansculottides, themeOfLeapDay, revolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeOfLeapDay Context triple: [Sansculottides, themeOfLeapDay, revolution]
-
A.
basisOfLeapYears
Indicates the rule or principle used to determine which calendar years are designated as leap years.
-
B.
leapMonthDeterminedBy
Indicates that the occurrence or placement of a leap month is determined or governed by the referenced entity or rule.
-
C.
rethemeYear
Indicates the year in which something (such as a product, event, or venue) is given a new theme or is thematically redesigned.
-
D.
hasFirstDayNameInLeapYear2020
Indicates that the entity’s first day (such as the start date of an event or period) falls on a specific named day in the leap year 2020.
-
E.
hasDayTheme
Indicates that something is associated with or characterized by a theme specifically intended for daytime use or context.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f131b1481909ff099c3b844ee07 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:31 a.m.