Triple
T17269345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of the Italian Glories |
E419210
|
entity |
| Predicate | hasFunctionOfBuilding |
P16394
|
FINISHED |
| Object | basilica |
—
|
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: basilica | Statement: [Temple of the Italian Glories, hasFunctionOfBuilding, basilica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionOfBuilding Context triple: [Temple of the Italian Glories, hasFunctionOfBuilding, basilica]
-
A.
hasBuildingFunction
chosen
Indicates that a building is used for or serves a particular function or purpose.
-
B.
functionInBuilding
Indicates that a specific function, role, or use is carried out within a particular building.
-
C.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
D.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
-
E.
hasBuildingComponent
Indicates that one entity includes, contains, or is composed of another entity as a physical building component.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4803b48190894b3bb9a4970602 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.