Triple
T25230323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himmela |
E632202
|
entity |
| Predicate | locationRelativeToStage |
P173332
|
FINISHED |
| Object | backstage |
—
|
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: backstage | Statement: [Himmela, locationRelativeToStage, backstage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRelativeToStage Context triple: [Himmela, locationRelativeToStage, backstage]
-
A.
locationRelativeToBorder
Indicates the position or placement of something in relation to a specified border or boundary.
-
B.
positionRelativeToSurface
Indicates how an entity is spatially located or oriented with respect to a reference surface.
-
C.
positionInFrame
Indicates the spatial location or coordinates of an entity within a specific frame or reference image.
-
D.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
-
E.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
- F. None of above. chosen
Provenance (4 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 21, 2026, 1:04 p.m.