Triple
T27703877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nephilim |
E698495
|
entity |
| Predicate | canTransformFrom |
P634
|
FINISHED |
| Object | mundane |
—
|
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: mundane | Statement: [Nephilim, canTransformFrom, mundane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canTransformFrom Context triple: [Nephilim, canTransformFrom, mundane]
-
A.
canTransform
Indicates that one entity is capable of being changed or converted into another entity or state.
-
B.
convertsFrom
chosen
Indicates that one entity is transformed or changed into another entity, with the source being the starting form or state.
-
C.
hasTransformationType
Indicates that an entity undergoes or is associated with a specific kind or category of transformation.
-
D.
acceptsConversionFrom
Indicates that one entity can validly receive or handle a conversion from another entity’s type, format, or representation.
-
E.
adaptsFrom
Indicates that one entity is derived, modified, or transformed from another, preserving core elements while changing form, medium, or 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635a522248190a3c43a4a6aa65e1f |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:58 p.m.