Triple
T24609362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otiorhynchus sulcatus |
E609071
|
entity |
| Predicate | lifeStageDamage |
P156735
|
FINISHED |
| Object | larvae damage roots and crowns |
—
|
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: larvae damage roots and crowns | Statement: [Otiorhynchus sulcatus, lifeStageDamage, larvae damage roots and crowns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeStageDamage Context triple: [Otiorhynchus sulcatus, lifeStageDamage, larvae damage roots and crowns]
-
A.
lifeStageAtDeath
Indicates the life stage or age category an entity was in at the time of its death.
-
B.
damageLeadsTo
Indicates that one instance of damage causally results in or contributes to another specified outcome or condition.
-
C.
damageTo
Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
-
D.
lifeStage
Indicates the specific phase or period in an entity’s development or lifecycle that it is currently in.
-
E.
damageOccurred
Indicates that some form of harm, loss, or deterioration has taken place as a result of an event or action.
- F. None of above. chosen
Provenance (4 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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:31 a.m.