Triple
T35418322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porta Fiorentina |
E1023707
|
entity |
| Predicate | locatedInFortifiedTown |
P182052
|
FINISHED |
| Object | Renaissance fortress-town Terra del Sole |
E312878
|
NE 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: Renaissance fortress-town Terra del Sole | Statement: [Porta Fiorentina, locatedInFortifiedTown, Renaissance fortress-town Terra del Sole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFortifiedTown Context triple: [Porta Fiorentina, locatedInFortifiedTown, Renaissance fortress-town Terra del Sole]
-
A.
isInFortifiedTown
chosen
Indicates that an entity is located within a town that is protected by defensive structures or fortifications.
-
B.
locatedInFortress
Indicates that an entity is situated within the boundaries or interior of a fortress.
-
C.
fortifiedIn
Indicates that one entity has been strengthened, reinforced, or protected within or by another entity (such as a structure, location, or medium).
-
D.
withinFortifications
Indicates that one entity is located inside the defensive structures or fortifications of another entity.
-
E.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
- F. None of above.
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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3836b3b03c819094bcb32130a37495 |
completed | June 21, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.