Triple
T38620371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lena Oxton |
E936848
|
entity |
| Predicate | resolvesConditionWith |
P191646
|
FINISHED |
| Object | Winston's chronal accelerator |
—
|
NE NERFINISHED |
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: Winston's chronal accelerator | Statement: [Lena Oxton, resolvesConditionWith, Winston's chronal accelerator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolvesConditionWith Context triple: [Lena Oxton, resolvesConditionWith, Winston's chronal accelerator]
-
A.
evaluatesCondition
Indicates that an entity assesses whether a specified condition or set of conditions holds true, typically producing a boolean result.
-
B.
resolvesTo
Indicates that one entity is mapped, translated, or evaluated into another specific entity as its target or result.
-
C.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
D.
supportsCondition
Indicates that one entity helps maintain, enable, or is compatible with a particular condition or state in another entity.
-
E.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce54532948190a5cfacfe18e09322 |
completed | May 7, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:32 p.m.