Triple
T27100632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L’Enfer |
E686427
|
entity |
| Predicate | hasAuthorImprisonmentContext |
P130308
|
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: [L’Enfer, hasAuthorImprisonmentContext, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorImprisonmentContext Context triple: [L’Enfer, hasAuthorImprisonmentContext, yes]
-
A.
hasBeenImprisoned
Indicates that an entity has been confined or incarcerated in a prison or similar detention facility at some point in time.
-
B.
hasBeenImprisonedBy
Indicates that one entity has been confined or incarcerated under the authority or control of another entity.
-
C.
timeOfAuthorImprisonment
chosen
Indicates the specific time period during which an author was imprisoned.
-
D.
hasPrison
Indicates that one entity possesses, contains, or is the location of a prison associated with another entity.
-
E.
imprisonmentContext
Indicates that one entity is held in confinement or custody by another entity or authority within a specific legal, temporal, or situational context.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 8:47 a.m.