Triple
T6205112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapindaceae |
E138725
|
entity |
| Predicate | notableTimber |
P1357
|
FINISHED |
| Object | maple 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: maple wood | Statement: [Sapindaceae, notableTimber, maple wood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTimber Context triple: [Sapindaceae, notableTimber, maple wood]
-
A.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
B.
notableVarieties
Indicates that there are specific, distinguished types or versions associated with an entity that are recognized as notable.
-
C.
notableForestAreas
Indicates that there exists a forested region associated with the subject that is recognized as significant or noteworthy in some context.
-
D.
woodProperty
chosen
Indicates that one entity specifies or characterizes a property or attribute of wood associated with another entity.
-
E.
notableBase
Indicates that a particular location serves as a significant or distinguished base or headquarters for an 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626d96ec8190816c00c44668177d |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.