Triple
T8806069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santo Spirito, Florence |
E209534
|
entity |
| Predicate | hasNaves |
P17652
|
FINISHED |
| Object | three naves |
—
|
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: three naves | Statement: [Santo Spirito, Florence, hasNaves, three naves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNaves Context triple: [Santo Spirito, Florence, hasNaves, three naves]
-
A.
hasNave
Indicates that one entity (typically a building or structure) possesses or includes a nave as a distinct architectural part.
-
B.
hasNavePlan
Indicates that an entity possesses or is associated with a specific plan or layout for a nave (the central part of a church or similar building).
-
C.
numberOfNaves
chosen
Indicates the specific count of naves (longitudinal sections) that a building, typically a church, possesses.
-
D.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
-
E.
hasShuttlecraft
Indicates that an entity possesses, controls, or is equipped with one or more shuttlecraft.
- 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_69ca836320e48190b5cf585b90a322c4 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd1f1a08190a2e584f6b0495f5c |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.