Triple
T6214070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astronium |
E138940
|
entity |
| Predicate | timberUse |
P1272
|
FINISHED |
| Object | structural applications |
—
|
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: structural applications | Statement: [Astronium, timberUse, structural applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timberUse Context triple: [Astronium, timberUse, structural applications]
-
A.
woodProperty
Indicates that one entity specifies or characterizes a property or attribute of wood associated with another entity.
-
B.
forestryActivity
Indicates activities related to the management, use, or cultivation of forest resources, such as logging, planting, or forest maintenance.
-
C.
constructionUsed
Indicates that one entity was employed as a construction method, material, or component in creating or assembling another entity.
-
D.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
E.
biomassContribution
Indicates the proportion or amount that an entity adds to the total biomass within a given system or context.
- 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_69c008ada364819096c9e92c74d639b5 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0629fd3c08190a121097c188417c4 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.