Triple
T37359318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deh vieni, non tardar |
E927535
|
entity |
| Predicate | placeInAct |
P98770
|
FINISHED |
| Object | near the end of Act IV |
—
|
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: near the end of Act IV | Statement: [Deh vieni, non tardar, placeInAct, near the end of Act IV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInAct Context triple: [Deh vieni, non tardar, placeInAct, near the end of Act IV]
-
A.
positionInAct
chosen
Indicates the specific location or role that something occupies within a particular act or segment of a larger sequence or performance.
-
B.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
C.
placeInDiscourse
Indicates the position or role that an element occupies within the structure or flow of a discourse or conversation.
-
D.
hasPlaceIn
Indicates that one entity occupies, is located within, or holds a specific position in another entity or context.
-
E.
posedIn
Indicates that an entity assumed a particular physical position or posture, typically for the purpose of being observed, photographed, drawn, or otherwise depicted.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:16 p.m.