Triple
T29721998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire (L’enfant et les sortilèges) |
E752077
|
entity |
| Predicate | relatedElement |
P37
|
FINISHED |
| Object | Fire (classical element) |
E752077
|
NE 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: Fire (classical element) | Statement: [Fire (L’enfant et les sortilèges), relatedElement, Fire (classical element)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedElement Context triple: [Fire (L’enfant et les sortilèges), relatedElement, Fire (classical element)]
-
A.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
C.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
D.
relatedAttribute
Indicates that one attribute is associated with, derived from, or otherwise contextually linked to another attribute.
-
E.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
- F. None of above.
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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a01a18e350481909f848686568d19bc |
completed | May 11, 2026, 9:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26aa7fd0ec8190b51d75056bbbdd13 |
completed | June 8, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a01a121b67c81908a6c5be9eb8e9ca5 |
completed | May 11, 2026, 9:28 a.m. |
Created at: April 28, 2026, 7:37 p.m.