Triple
T20433047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | chancery of the Republic of Florence |
E501179
|
entity |
| Predicate | existedInGovernmentType |
P62479
|
FINISHED |
| Object | republic |
—
|
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: republic | Statement: [chancery of the Republic of Florence, existedInGovernmentType, republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existedInGovernmentType Context triple: [chancery of the Republic of Florence, existedInGovernmentType, republic]
-
A.
basedInGovernmentType
chosen
Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
-
B.
laterGovernmentType
Indicates that one government type succeeds or replaces another at a later point in time.
-
C.
servedInGovernmentWith
Indicates that two individuals held positions in the same government or administration during an overlapping period of time.
-
D.
hasGovernmentalBodyType
Indicates the specific kind or classification of governmental body that an entity possesses or is associated with.
-
E.
targetGovernmentType
Indicates the form or system of governance that an entity is directed toward, associated with, or intended to influence.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685eba35881908c316443b6d789fb |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:31 a.m.