Triple
T3378851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alan-a-Dale |
E71130
|
entity |
| Predicate | adaptationRole |
P28456
|
FINISHED |
| Object | narrator in some Robin Hood adaptations |
—
|
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: narrator in some Robin Hood adaptations | Statement: [Alan-a-Dale, adaptationRole, narrator in some Robin Hood adaptations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptationRole Context triple: [Alan-a-Dale, adaptationRole, narrator in some Robin Hood adaptations]
-
A.
adaptationType
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
B.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
C.
roleInEcosystem
Indicates the specific function or contribution an entity has within an ecosystem and how it interacts with other components of that system.
-
D.
possibleRole
chosen
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
E.
adaptationBy
Indicates a relationship where one entity has been modified, transformed, or reworked by another entity into a new form or version.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2eacb5c81908071a1dacc9a897a |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.