Triple
T22104167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prayer for Marius Pontmercy |
E546243
|
entity |
| Predicate | hasTargetOutcome |
P14889
|
FINISHED |
| Object | Marius Pontmercy’s survival |
—
|
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: Marius Pontmercy’s survival | Statement: [Prayer for Marius Pontmercy, hasTargetOutcome, Marius Pontmercy’s survival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetOutcome Context triple: [Prayer for Marius Pontmercy, hasTargetOutcome, Marius Pontmercy’s survival]
-
A.
hasOutcomeIndicator
Indicates that something is associated with a specific measure or indicator used to evaluate its outcome or results.
-
B.
hasEventOutcome
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
-
C.
hasTarget
chosen
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
D.
hasProposedOutcome
Indicates that an action, decision, or process is associated with a suggested or anticipated result that is being put forward but not yet realized or confirmed.
-
E.
hasConclusion
Indicates that something leads to, results in, or is associated with a particular conclusion.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1291815f88190a6eaf73e444dc1c2 |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.