Triple
T3504808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craft Center |
E74049
|
entity |
| Predicate | hasInterpretiveApproach |
P10363
|
FINISHED |
| Object | hands-on learning |
—
|
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: hands-on learning | Statement: [Craft Center, hasInterpretiveApproach, hands-on learning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterpretiveApproach Context triple: [Craft Center, hasInterpretiveApproach, hands-on learning]
-
A.
hasInterpretiveSigns
Indicates that interpretive or informational signs are present at or associated with the subject.
-
B.
interpretationMethod
Indicates the method, technique, or process used to interpret or derive meaning from something.
-
C.
hasInterpretiveExhibits
Indicates that an entity includes or provides exhibits designed to explain, interpret, or contextualize information for viewers.
-
D.
containsInterpretationOf
Indicates that one entity includes or embodies an interpretation or understanding of another entity.
-
E.
includesApproach
chosen
Indicates that one entity incorporates, utilizes, or is characterized by a particular method, strategy, or approach in relation to another entity or context.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf22b1c8190956141d8fb924210 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.