Triple
T33745578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuol Svay Prey High School |
E864688
|
entity |
| Predicate | buildingTypeAfterConversion |
P73483
|
FINISHED |
| Object | security prison |
—
|
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: security prison | Statement: [Tuol Svay Prey High School, buildingTypeAfterConversion, security prison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingTypeAfterConversion Context triple: [Tuol Svay Prey High School, buildingTypeAfterConversion, security prison]
-
A.
buildingConvertedTo
chosen
Indicates that one building has been transformed, repurposed, or adapted into another type or use of building.
-
B.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
C.
originalBuildingType
Indicates the type or category of building that something was initially constructed or designated to be, before any later changes or repurposing.
-
D.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
E.
intendedBuildingType
Indicates the type of building that something is planned or designed to be.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:44 a.m.