Triple
T22824759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Security Housing Unit |
E565621
|
entity |
| Predicate | placementBasedOn |
P54922
|
FINISHED |
| Object | risk assessment |
—
|
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: risk assessment | Statement: [Security Housing Unit, placementBasedOn, risk assessment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placementBasedOn Context triple: [Security Housing Unit, placementBasedOn, risk assessment]
-
A.
positionBased
Indicates a relationship determined by the relative or absolute position of entities, where the connection depends on where they are located rather than on their intrinsic properties.
-
B.
placementType
Indicates the specific manner or category in which something is positioned, arranged, or assigned within a given context.
-
C.
basedOnBy
chosen
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
D.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
E.
positionUse
Indicates how a particular position or role is utilized or functionally applied within a given context.
- 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dd34a248190881f2bccdd9aedce |
completed | April 29, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:34 p.m.