Triple
T19938318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanjo Ohashi |
E479234
|
entity |
| Predicate | hasPredecessorMaterial |
P104310
|
FINISHED |
| Object | wood |
—
|
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: wood | Statement: [Sanjo Ohashi, hasPredecessorMaterial, wood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPredecessorMaterial Context triple: [Sanjo Ohashi, hasPredecessorMaterial, wood]
-
A.
hasPredecessorStructureFrom
Indicates that one structure existed or was established before another structure in a sequential or developmental order.
-
B.
hasPredecessorRoleIn
Indicates that one role functioned earlier in time or sequence relative to another role within the same context or position.
-
C.
replacedMaterialOfPredecessor
chosen
Indicates that one entity represents the material that has taken the place of, or superseded, the material used in its predecessor entity.
-
D.
hasPrecedingWork
Indicates that one work comes before another in a sequence, serving as its predecessor.
-
E.
hasParentMaterial
Indicates that one entity is derived from, formed in, or directly associated with another entity that serves as its original or underlying material.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a190ac08190b9dc7955c9764a71 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.