Triple
T20048125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palazzo Brignole Sale |
E497616
|
entity |
| Predicate | isInEnsemble |
P49020
|
FINISHED |
| Object | system of the Palazzi dei Rolli in Genoa |
—
|
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: system of the Palazzi dei Rolli in Genoa | Statement: [Palazzo Brignole Sale, isInEnsemble, system of the Palazzi dei Rolli in Genoa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInEnsemble Context triple: [Palazzo Brignole Sale, isInEnsemble, system of the Palazzi dei Rolli in Genoa]
-
A.
isPartOfEnsemble
chosen
Indicates that an entity belongs to, or is a member of, a larger group or ensemble.
-
B.
hasEnsembleRoleWith
Indicates that two or more entities share a collaborative or joint role within the same ensemble, group, or collective context.
-
C.
hasEnsembles
Indicates that an entity is associated with one or more ensembles, typically as a member, component, or participant.
-
D.
hasEnsembleNumbers
Indicates that an entity is associated with one or more ensemble numbers used to identify it within a grouped or collective context.
-
E.
typeOfEnsemble
Indicates the specific kind or category of ensemble that an entity belongs to or represents.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632c085081908710cbc939ac9971 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.