Triple
T13250550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angora goat |
E315514
|
entity |
| Predicate | fiberMicronRange |
P35372
|
FINISHED |
| Object | approximately 24–40 microns |
—
|
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: approximately 24–40 microns | Statement: [Angora goat, fiberMicronRange, approximately 24–40 microns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fiberMicronRange Context triple: [Angora goat, fiberMicronRange, approximately 24–40 microns]
-
A.
wavelengthRangeLowerBoundMicrometers
Indicates the minimum wavelength value, expressed in micrometers, that defines the lower limit of a wavelength range for the related entity or measurement.
-
B.
grainSize
Indicates the relative coarseness or fineness of the material or particles involved in the relationship.
-
C.
fiberType
Indicates the specific kind or classification of fiber that characterizes or composes an entity.
-
D.
needlesPerFascicle
Indicates the number of individual needles contained within a single fascicle (bundle) of needles.
-
E.
fiberCharacteristic
chosen
Indicates a relationship where a specific characteristic or property is attributed to a fiber or fibrous material.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:24 p.m.