Triple
T8583357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludovica Military Academy |
E203239
|
entity |
| Predicate | buildingUseAfterDissolution |
P42263
|
FINISHED |
| Object | military barracks |
—
|
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: military barracks | Statement: [Ludovica Military Academy, buildingUseAfterDissolution, military barracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingUseAfterDissolution Context triple: [Ludovica Military Academy, buildingUseAfterDissolution, military barracks]
-
A.
buildingUseAfterClosure
Indicates how a building is used or repurposed after its original function or operation has ceased.
-
B.
siteUseAfterDemolition
Indicates the subsequent use or function assigned to a site following the demolition of its previous structures.
-
C.
buildingReuseType
chosen
Indicates the manner or purpose for which an existing building is reused or repurposed.
-
D.
previousBuildingUse
Indicates that a building previously served a specified use or function before its current one.
-
E.
functionAfterDissolution
Indicates that one function, role, or operation occurs or continues after the dissolution or termination of another entity or structure.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbeb1d0edc8190b4495935275252f3 |
completed | March 31, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:22 p.m.