Triple
T17850345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean II, Duke of Alençon |
E445782
|
entity |
| Predicate | releasedByRansom |
P39673
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Jean II, Duke of Alençon, releasedByRansom, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedByRansom Context triple: [Jean II, Duke of Alençon, releasedByRansom, yes]
-
A.
ransomPaid
chosen
Indicates that a payment has been made to secure the release of a person, property, or information held under threat or coercion.
-
B.
ransom
Indicates demanding payment or concessions in exchange for releasing a person, object, or information held under threat or coercion.
-
C.
releaseFrom
Indicates that one entity causes or authorizes another entity to be freed, discharged, or removed from a prior state of confinement, obligation, or restriction.
-
D.
releasedInsteadOf
Indicates that one entity was released in place of, or as a substitute for, another entity that was not released.
-
E.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ffe415c8190aed351c52b78a143 |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.