Triple
T7751563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Stephen’s College massacre |
E175773
|
entity |
| Predicate | usedBuildingAs |
P65370
|
FINISHED |
| Object | makeshift military hospital |
—
|
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: makeshift military hospital | Statement: [St. Stephen’s College massacre, usedBuildingAs, makeshift military hospital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBuildingAs Context triple: [St. Stephen’s College massacre, usedBuildingAs, makeshift military hospital]
-
A.
usesBuilding
Indicates that one entity makes use of, occupies, or operates within a particular building.
-
B.
appliedToBuilding
Indicates that something (such as a process, treatment, regulation, or attribute) is directed toward, implemented on, or otherwise affects a building.
-
C.
previousBuildingUse
Indicates that a building previously served a specified use or function before its current one.
-
D.
locatedInBuildingUsedAs
chosen
Indicates that something is located inside a building that is being used for a specified purpose or function.
-
E.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
- 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_69c69960b3588190a53aa590d31d9544 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:08 p.m.