Triple
T27740432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve |
E701837
|
entity |
| Predicate | hasMagicProperty |
P197256
|
FINISHED |
| Object | brought to life by magic spell |
—
|
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: brought to life by magic spell | Statement: [Eve, hasMagicProperty, brought to life by magic spell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagicProperty Context triple: [Eve, hasMagicProperty, brought to life by magic spell]
-
A.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
B.
hasProtectedProperty
Indicates that an entity possesses a property or attribute that is designated as protected, meaning it is restricted or shielded from general access or modification.
-
C.
hasMagicItem
Indicates that an entity possesses or is associated with a magical item.
-
D.
hasPropertyT
Indicates that an entity possesses or is characterized by a specific property T.
-
E.
hasPropertyFlag
Indicates that an entity possesses a specific property denoted by a particular flag or marker.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
| PDg | Predicate description generation | batch_69fe831ba4708190a5564afd7d5a4319 |
completed | May 9, 2026, 12:43 a.m. |
Created at: April 27, 2026, 4:10 p.m.