Triple
T27283063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossarchus obscurus |
E688389
|
entity |
| Predicate | furTexture |
P4016
|
FINISHED |
| Object | coarse |
—
|
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 | Statement: [Crossarchus obscurus, furTexture, coarse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: furTexture Context triple: [Crossarchus obscurus, furTexture, coarse]
-
A.
furPattern
Indicates the type or arrangement of fur markings or coloration that characterizes an entity’s coat.
-
B.
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.
-
C.
typicalTexture
Indicates the usual or characteristic surface feel or consistency that is commonly associated with an entity.
-
D.
fleshTexture
Indicates the tactile quality or surface feel of an entity’s flesh, such as how smooth, firm, soft, or coarse it is.
-
E.
fur
Indicates that one entity has fur covering its body or surface.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6275281288190baf993960cf87fac |
completed | May 2, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:09 a.m.