Triple
T8433378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Groot |
E199167
|
entity |
| Predicate | speciesTrait |
P40326
|
FINISHED |
| Object | can regrow from small fragments |
—
|
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: can regrow from small fragments | Statement: [Groot, speciesTrait, can regrow from small fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesTrait Context triple: [Groot, speciesTrait, can regrow from small fragments]
-
A.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
B.
biologicalCharacteristic
chosen
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
C.
ecotypeOf
Indicates that one entity is an ecotype, i.e., a locally adapted variant or form, of another entity within the same species.
-
D.
speciesStructure
Indicates the structural or organizational characteristics that define how a species is composed or arranged.
-
E.
shareBiodiversityFeature
Indicates that two or more entities have a biodiversity-related characteristic, attribute, or feature in common.
- 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_69ca8313c99081909a5c6d83b91de5b3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:07 p.m.