Triple
T24201996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Il re pastore |
E600005
|
entity |
| Predicate | notableSettingType |
P155160
|
FINISHED |
| Object | serenata |
—
|
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: serenata | Statement: [Il re pastore, notableSettingType, serenata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSettingType Context triple: [Il re pastore, notableSettingType, serenata]
-
A.
notableSetting
Indicates that a particular place or environment is especially significant or prominent as the context in which an entity is situated or occurs.
-
B.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
-
C.
notableMode
Indicates that the subject is recognized for or distinguished by the specified mode, manner, or method of operation or expression.
-
D.
notableStoreType
Indicates that a store is particularly recognized or distinguished for being of a specified type (e.g., a notable example of that kind of store).
-
E.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca1f3b481908c14052a8435fd21 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:36 p.m.