Triple
T26825657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morrígan |
E675370
|
entity |
| Predicate | canTakeFormOf |
P90593
|
FINISHED |
| Object | eel |
—
|
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: eel | Statement: [Morrígan, canTakeFormOf, eel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canTakeFormOf Context triple: [Morrígan, canTakeFormOf, eel]
-
A.
takesFormOf
Indicates that one entity assumes, manifests, or is expressed in the shape, structure, or configuration of another entity.
-
B.
canTakeForm
chosen
Indicates that one entity is capable of assuming, transforming into, or being represented as the form or appearance of another entity.
-
C.
isFormedFor
Indicates that something is created, established, or brought into existence for a particular purpose, function, or beneficiary.
-
D.
hasRealFormOf
Indicates that one entity is the concrete, real-world manifestation or physical form of another, more abstract or conceptual entity.
-
E.
mayBeFormedWhen
Indicates that one entity has the potential to come into existence or be created as a result of another entity, condition, or process.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 4:58 a.m.