Triple
T4496019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urera |
E100696
|
entity |
| Predicate | stingingStructure |
P53081
|
FINISHED |
| Object | urticating hairs |
—
|
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: urticating hairs | Statement: [Urera, stingingStructure, urticating hairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stingingStructure Context triple: [Urera, stingingStructure, urticating hairs]
-
A.
survivingStructure
Indicates that a structure continues to exist or remain intact after a potentially destructive event or over a significant period of time.
-
B.
hasStingingHairs
chosen
Indicates that an entity possesses hairs capable of delivering a sting or irritation upon contact.
-
C.
massiveStructure
Indicates that an entity is a very large or imposing physical structure in terms of size, scale, or mass.
-
D.
defensiveStructure
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
-
E.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56bde14c819091d42839a46291d0 |
completed | March 20, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.