Triple
T17366326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luffa cylindrica |
E422196
|
entity |
| Predicate | textureOfSponge |
P4016
|
FINISHED |
| Object | coarse and fibrous |
—
|
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: coarse and fibrous | Statement: [Luffa cylindrica, textureOfSponge, coarse and fibrous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textureOfSponge Context triple: [Luffa cylindrica, textureOfSponge, coarse and fibrous]
-
A.
texture
chosen
Indicates the surface quality or feel of an entity as perceived by touch or appearance, such as being smooth, rough, soft, or coarse.
-
B.
textureCharacteristicInFugue
Indicates that a specified texture characteristic is present or manifested within a particular fugue.
-
C.
typicalTexture
Indicates the usual or characteristic surface feel or consistency that is commonly associated with an entity.
-
D.
textureOfCenter
Indicates the texture characteristic specifically associated with the central part of an object or region.
-
E.
fleshTexture
Indicates the tactile quality or surface feel of an entity’s flesh, such as how smooth, firm, soft, or coarse it is.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a50c9ec8190b518fdf80808af53 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.