Triple
T28002423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the mirror stage |
E707182
|
entity |
| Predicate | statusInLacan |
P186452
|
FINISHED |
| Object | revised and reinterpreted across Lacan’s seminars |
—
|
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: revised and reinterpreted across Lacan’s seminars | Statement: [the mirror stage, statusInLacan, revised and reinterpreted across Lacan’s seminars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInLacan Context triple: [the mirror stage, statusInLacan, revised and reinterpreted across Lacan’s seminars]
-
A.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
-
B.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
C.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
statusInSira
Indicates the status or standing that an entity holds within the Sira system or classification.
-
E.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: April 27, 2026, 7:57 p.m.