Triple
T36947542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Enders |
E913955
|
entity |
| Predicate | roleInPlayRevival |
P66423
|
FINISHED |
| Object | Helena |
unclear NED1
|
NE 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: Helena | Statement: [Maria Enders, roleInPlayRevival, Helena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPlayRevival Context triple: [Maria Enders, roleInPlayRevival, Helena]
-
A.
revivalVersionRole
chosen
Indicates the role or function an entity has in relation to a particular version of a revival (e.g., a new staging, edition, or re-release) of a work or event.
-
B.
roleInNavigationRevival
Indicates that an entity played a part in the restoration, resurgence, or renewed use of navigation practices or systems.
-
C.
revivedAs
Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
-
D.
revivalLeadActor
Indicates that the subject is the lead actor in a revival (new production or version) of the related work or performance.
-
E.
returnInRevival
Indicates that an entity comes back or is brought back during a revival event or period.
- F. None of above.
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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01c303af6081909c229b2c8e91c680 |
completed | May 11, 2026, 11:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c34013c81908e59c15db9e68d18 |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a01c28ebf54819094318c447d8c7943 |
completed | May 11, 2026, 11:50 a.m. |
Created at: May 3, 2026, 4:13 p.m.