Triple
T28002382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the mirror stage |
E707182
|
entity |
| Predicate | fullyFormulatedIn |
P163615
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [the mirror stage, fullyFormulatedIn, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullyFormulatedIn Context triple: [the mirror stage, fullyFormulatedIn, 1949]
-
A.
isFormulatedUsing
Indicates that something is created, defined, or expressed by means of a specified method, material, or set of components.
-
B.
isFormulatedBy
Indicates that something (such as a plan, idea, or substance) is created, devised, or composed by a particular agent or source.
-
C.
coFormulated
Indicates that two or more entities were jointly formulated, designed, or created together as part of the same process or product.
-
D.
hasFormulation
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
E.
formulatedAfter
Indicates that one entity was created, developed, or formally established subsequent to and typically influenced by another entity.
- 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_69f63bd2dc3c81908ee2471fa32c7841 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 7:57 p.m.