Triple
T6822309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wigwam |
E156927
|
entity |
| Predicate | hasFrameworkMaterial |
P49659
|
FINISHED |
| Object | Wooden poles |
—
|
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: Wooden poles | Statement: [Wigwam, hasFrameworkMaterial, Wooden poles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrameworkMaterial Context triple: [Wigwam, hasFrameworkMaterial, Wooden poles]
-
A.
hasMaterialAspect
Indicates that something possesses a physical or tangible component or aspect as part of its overall nature or existence.
-
B.
featuresMaterialFrom
chosen
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
C.
hasReconstructionMaterial
Indicates that something is associated with, composed of, or utilizes a particular material for its reconstruction.
-
D.
supportsMaterial
Indicates that one entity provides structural or functional support to a material entity, enabling it to be held, stabilized, or borne.
-
E.
hasMaterialOption
Indicates that an entity can be made from, or is available in, one or more alternative materials.
- 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_69c688298a288190af3f285d57f76bbe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d57f69cc8190bbd08a8d447e616f |
completed | March 27, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:17 p.m.