Triple
T20994266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide’s Lament |
E517104
|
entity |
| Predicate | isNumberInAct |
P142399
|
FINISHED |
| Object | Act I (typical staging) |
—
|
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: Act I (typical staging) | Statement: [Adelaide’s Lament, isNumberInAct, Act I (typical staging)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberInAct Context triple: [Adelaide’s Lament, isNumberInAct, Act I (typical staging)]
-
A.
hasNumberInActa
Indicates that an entity is associated with a specific identifying number recorded in an official acta (formal record or document).
-
B.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
C.
positionInAct
Indicates the specific location or role that something occupies within a particular act or segment of a larger sequence or performance.
-
D.
activeInBand
Indicates that an entity is a current member performing or participating in the activities of a specific band.
-
E.
isActually
Indicates that something is in fact a particular way or identity, often clarifying or correcting a previous or apparent understanding.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc1e75188190a97114238ea0b4f9 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:50 p.m.