Triple
T6131460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philyra |
E136727
|
entity |
| Predicate | requestedTransformationFrom |
P34717
|
FINISHED |
| Object | the gods |
—
|
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: the gods | Statement: [Philyra, requestedTransformationFrom, the gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestedTransformationFrom Context triple: [Philyra, requestedTransformationFrom, the gods]
-
A.
requestedFrom
chosen
Indicates that one entity has made a request to another entity as the source or provider of something.
-
B.
transformType
Indicates that one entity is converted or changed from its original form into another specified type or form.
-
C.
transformsUnder
Indicates a relationship where one entity changes form, state, or structure when subjected to the influence, conditions, or operation specified by another entity.
-
D.
featuresTransformationOf
Indicates that something includes or presents a transformation or change applied to another entity.
-
E.
regionTransformed
Indicates that one region has been changed or converted into another region through some transformation 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c4f7ad8819096b09ddd312453fb |
completed | March 22, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:15 p.m.