Triple
T18061617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fire in the Borgo |
E432186
|
entity |
| Predicate | wallPosition |
P125898
|
FINISHED |
| Object | east wall of the Stanza dell’Incendio di Borgo |
—
|
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: east wall of the Stanza dell’Incendio di Borgo | Statement: [The Fire in the Borgo, wallPosition, east wall of the Stanza dell’Incendio di Borgo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wallPosition Context triple: [The Fire in the Borgo, wallPosition, east wall of the Stanza dell’Incendio di Borgo]
-
A.
wallFeature
Indicates that one entity functions as a structural or design feature associated with a wall of another entity.
-
B.
wallPlan
Indicates a planned or designed configuration of walls within a space or structure.
-
C.
wallCharacteristic
chosen
Indicates that a specified characteristic or property is attributed to a wall.
-
D.
hasWall
Indicates that one entity possesses, includes, or is bounded by a wall.
-
E.
wallMaterial
Indicates that one entity is the material from which a wall or walls of another entity are constructed.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c107351c8190a2bfdb46754c2c6e |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.