Triple
T8567045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appalachian Spring |
E202830
|
entity |
| Predicate | usesFolkMaterialFrom |
P1272
|
FINISHED |
| Object | Shaker tradition |
—
|
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: Shaker tradition | Statement: [Appalachian Spring, usesFolkMaterialFrom, Shaker tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFolkMaterialFrom Context triple: [Appalachian Spring, usesFolkMaterialFrom, Shaker tradition]
-
A.
traditionalMaterial
Indicates that something is made from, incorporates, or is characterized by materials associated with long-established or customary practices.
-
B.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
C.
materialInLore
Indicates that a material is referenced, described, or plays a role within a body of lore or fictional/worldbuilding context.
-
D.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
-
E.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9d467c08190b2014d71ebbf8bbc |
completed | March 31, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.