Triple
T23532211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nina Zarechnaya |
E576599
|
entity |
| Predicate | arcOutcome |
P59870
|
FINISHED |
| Object | acceptance of hardship and commitment to acting |
—
|
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: acceptance of hardship and commitment to acting | Statement: [Nina Zarechnaya, arcOutcome, acceptance of hardship and commitment to acting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arcOutcome Context triple: [Nina Zarechnaya, arcOutcome, acceptance of hardship and commitment to acting]
-
A.
arc
Indicates a directed relationship from one entity to another, often representing a one-way connection or transition between them.
-
B.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
C.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
D.
launchOutcome
Indicates the result or consequence of a launch event, such as whether it succeeded, failed, or had a specific status or outcome.
-
E.
outcomeOfTrial
Indicates that a particular result or verdict is produced as the consequence of a specific trial or legal proceeding.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac78581c8190bd9d09ce2be8029d |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.