Triple
T2995743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawrence (Westworld) |
E81060
|
entity |
| Predicate | resurrectedBy |
P7738
|
FINISHED |
| Object | park technicians |
—
|
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: park technicians | Statement: [Lawrence (Westworld), resurrectedBy, park technicians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resurrectedBy Context triple: [Lawrence (Westworld), resurrectedBy, park technicians]
-
A.
revivedBy
chosen
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
-
B.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
-
C.
focusDuringRevival
Indicates that one entity maintains or directs focused attention on another entity or process during a revival event or restoration phase.
-
D.
restoredBy
Indicates that an entity has been returned to a previous or improved state through the actions or intervention of another entity.
-
E.
resurrectionPlace
Indicates the location where an entity is brought back to life or restored from death.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f481688190ae8cd1e057f9dfc7 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.