Triple
T15976384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gironniera cuspidata |
E387458
|
entity |
| Predicate | woodUseContext |
P72822
|
FINISHED |
| Object | local timber markets |
—
|
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: local timber markets | Statement: [Gironniera cuspidata, woodUseContext, local timber markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: woodUseContext Context triple: [Gironniera cuspidata, woodUseContext, local timber markets]
-
A.
treeUse
chosen
Indicates the way in which a tree is utilized or purposed within a given context.
-
B.
woodProperty
Indicates that one entity specifies or characterizes a property or attribute of wood associated with another entity.
-
C.
topWood
Indicates that one entity is made of or features a particular type of wood used specifically for its top surface or top section.
-
D.
isWoodenStructure
Indicates that the subject is a structure primarily made of wood or constructed using wooden components.
-
E.
oakTypeUsed
Indicates that a particular type of oak is used in relation to another entity, such as in construction, manufacturing, or production.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.