Triple
T35309114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sly Fox |
E1019717
|
entity |
| Predicate | adapterOf |
P66478
|
FINISHED |
| Object | Volpone |
—
|
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: Volpone | Statement: [Sly Fox, adapterOf, Volpone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adapterOf Context triple: [Sly Fox, adapterOf, Volpone]
-
A.
officialAdapterFor
Indicates that one entity serves as the formally designated adapter or intermediary component for another entity.
-
B.
adaptsBy
Indicates that one entity changes, modifies, or adjusts itself, its behavior, or its form as a result of influence, guidance, or transformation performed by another entity.
-
C.
adaptsFrom
chosen
Indicates that one entity is derived, modified, or transformed from another, preserving core elements while changing form, medium, or context.
-
D.
adapterMustProvide
Indicates that an adapter is required to supply or implement a specified functionality, interface, or service.
-
E.
compatibleViaAdapterWith
Indicates that two entities, which are not directly compatible, can function together when connected through a specific adapter.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.