Triple
T13352577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angora rabbit |
E318104
|
entity |
| Predicate | fiberSource |
P53073
|
FINISHED |
| Object | rabbit fur |
—
|
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: rabbit fur | Statement: [Angora rabbit, fiberSource, rabbit fur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fiberSource Context triple: [Angora rabbit, fiberSource, rabbit fur]
-
A.
isCellulosicFiber
Indicates that a material or fiber is composed primarily of cellulose or derived from cellulose-based sources.
-
B.
fiberContent
Indicates that one entity specifies the amount or presence of dietary fiber contained in another entity.
-
C.
fiberType
Indicates the specific kind or classification of fiber that characterizes or composes an entity.
-
D.
fiberwiseDescription
Indicates a description or characterization that is given separately for each fiber in a fibered or parameterized structure, specifying how the relationship or action behaves over individual fibers.
-
E.
materialSource
chosen
Indicates that one entity serves as the origin or provider of the material or substance used by 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8d520881908aa23c7102b72b72 |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6fd8bc819086dddb6f376efa57 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:32 p.m.