Triple
T10409766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zygmunt Column (patronage) |
E245356
|
entity |
| Predicate | roleOfPatron |
P68473
|
FINISHED |
| Object | initiated construction of the monument |
—
|
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: initiated construction of the monument | Statement: [Zygmunt Column (patronage), roleOfPatron, initiated construction of the monument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfPatron Context triple: [Zygmunt Column (patronage), roleOfPatron, initiated construction of the monument]
-
A.
typeOfPatronage
Indicates the specific kind or category of support, sponsorship, or backing that one entity provides to another.
-
B.
primaryPatron
Indicates that one entity serves as the main or chief supporter, sponsor, or benefactor of another entity.
-
C.
laterPatron
Indicates that one entity serves as a patron of another at a later time than some reference patronage relationship.
-
D.
usedAsPatronOf
chosen
Indicates that one entity serves as a patron or sponsor for another, providing support, endorsement, or backing.
-
E.
traditionalPatron
Indicates a relationship where one entity serves as a customary or historically established patron or supporter of another.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9fb98748190a3a6c161edd8f400 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:09 p.m.