Triple
T10084324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wancho |
E215179
|
entity |
| Predicate | woodcarvingMotifs |
P48945
|
FINISHED |
| Object | human figures |
—
|
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: human figures | Statement: [Wancho, woodcarvingMotifs, human figures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: woodcarvingMotifs Context triple: [Wancho, woodcarvingMotifs, human figures]
-
A.
traditionalMotif
Indicates that something incorporates, represents, or is characterized by a motif rooted in established cultural or historical traditions.
-
B.
hasBranchCarvings
Indicates that an entity (such as a tree or wooden object) possesses carvings or engravings specifically on its branches.
-
C.
hasCarvings
chosen
Indicates that one entity features or contains carved designs or engravings on its surface, created by another entity or process.
-
D.
hasRootCarvings
Indicates that an object, typically a plant or tree, possesses carvings or engraved markings on its roots.
-
E.
hasCarving
Indicates that one entity features or contains a carved design, inscription, or sculpted detail that is associated with or applied to 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd044c1ec8190b5b48cdb0584d00c |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9 p.m.