Triple
T28974190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loba |
E734360
|
entity |
| Predicate | adaptedVersionOf |
P15523
|
FINISHED |
| Object | She Wolf |
—
|
NE NERFINISHED |
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: She Wolf | Statement: [Loba, adaptedVersionOf, She Wolf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptedVersionOf Context triple: [Loba, adaptedVersionOf, She Wolf]
-
A.
adaptedWithin
Indicates that one entity has been modified, adjusted, or tailored to function appropriately within the context, scope, or boundaries defined by another entity.
-
B.
adaptedAs
Indicates that one work, concept, or entity has been transformed or re-created into another form or medium based on the original.
-
C.
adaptedWorkOf
chosen
Indicates that one work is derived from, based on, or reinterprets the content of another pre-existing work.
-
D.
inspiredByAdaptationOf
Indicates that something draws its inspiration from an adaptation (rather than the original source) of another work or entity.
-
E.
adaptedTo
Indicates that one entity has been modified, adjusted, or evolved to function effectively within the conditions, requirements, or characteristics defined by another entity.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 9:07 a.m.