Triple
T13250566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angora goat |
E315514
|
entity |
| Predicate | shearingFrequency |
P85
|
FINISHED |
| Object | typically twice a year |
—
|
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: typically twice a year | Statement: [Angora goat, shearingFrequency, typically twice a year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shearingFrequency Context triple: [Angora goat, shearingFrequency, typically twice a year]
-
A.
frequency
chosen
Indicates how often an event, action, or relationship occurs within a given period or context.
-
B.
divisionFrequency
Indicates how often a division event occurs within a given context or time frame.
-
C.
frequencyShiftProperty
Indicates a relationship where one entity specifies or characterizes the amount or nature of a change in frequency experienced by another entity or signal.
-
D.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
E.
hasRotationFrequency
Indicates that one entity possesses or is characterized by a specific rate at which it rotates over time.
- 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.