Triple
T31249323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genoese republican system |
E796770
|
entity |
| Predicate | reformedSignificantlyInYear |
P61765
|
FINISHED |
| Object | 1528 |
—
|
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: 1528 | Statement: [Genoese republican system, reformedSignificantlyInYear, 1528]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformedSignificantlyInYear Context triple: [Genoese republican system, reformedSignificantlyInYear, 1528]
-
A.
reformedOn
Indicates that an entity underwent a reform, change, or restructuring at a specific point in time or on a particular date.
-
B.
reformationYear
chosen
Indicates the year in which an entity underwent a significant reform, restructuring, or reorganization.
-
C.
timeOfMajorReforms
Indicates the specific time period during which significant reforms or major changes took place.
-
D.
laterReformedAs
Indicates that an entity was subsequently reorganized, renamed, or transformed into another entity at a later time.
-
E.
reformedDueTo
Indicates that one entity has changed or improved its behavior, beliefs, or practices as a result of the influence, actions, or circumstances associated with another entity.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:11 p.m.