Triple
T21659530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorcerer |
E534556
|
entity |
| Predicate | includedMaterials |
P1393
|
FINISHED |
| Object | physical feelies |
—
|
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: physical feelies | Statement: [Sorcerer, includedMaterials, physical feelies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedMaterials Context triple: [Sorcerer, includedMaterials, physical feelies]
-
A.
materialProvidedFor
Indicates that one entity supplies or makes available a material for use, processing, or incorporation by another entity or purpose.
-
B.
additionalMaterialBy
Indicates that one entity serves as supplementary or supporting material created by a specified agent or source.
-
C.
supportsMaterial
Indicates that one entity provides structural or functional support to a material entity, enabling it to be held, stabilized, or borne.
-
D.
includesReworkedMaterialFrom
Indicates that one entity incorporates or is derived from modified, revised, or otherwise reworked material originating in another entity.
-
E.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c06844c81909b9c91e02fa4e6e1 |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.