Triple
T28332319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Il turco in Italia |
E717567
|
entity |
| Predicate | ProsdocimoRole |
P146141
|
FINISHED |
| Object | poet observing and shaping the plot |
—
|
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: poet observing and shaping the plot | Statement: [Il turco in Italia, ProsdocimoRole, poet observing and shaping the plot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ProsdocimoRole Context triple: [Il turco in Italia, ProsdocimoRole, poet observing and shaping the plot]
-
A.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
B.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
C.
profileRole
chosen
Indicates the specific role or function an entity holds within a given profile or contextual configuration.
-
D.
CorwinRole
Indicates that an entity holds or is assigned a specific role or function in relation to Corwin.
-
E.
providedRole
Indicates that one entity has assigned or supplied a specific role or function to 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64bcec4748190b71a5c9e9a66d843 |
completed | May 2, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:33 a.m.