Triple
T38641280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Hemp |
E938599
|
entity |
| Predicate | wasBredFor |
P191311
|
FINISHED |
| Object | working ability rather than appearance |
—
|
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: working ability rather than appearance | Statement: [Old Hemp, wasBredFor, working ability rather than appearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasBredFor Context triple: [Old Hemp, wasBredFor, working ability rather than appearance]
-
A.
wasBredIn
Indicates that an organism or animal was raised or produced through breeding in a particular place or environment.
-
B.
wasDomesticatedIn
Indicates that an entity became domesticated during or within a specified time period or historical era.
-
C.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
D.
bredWith
Indicates that one entity has been used to reproduce or mate with another entity, typically for the purpose of producing offspring.
-
E.
madeFromBreed
Indicates that something is produced or derived using a particular breed as its source or primary constituent.
- F. None of above. chosen
Provenance (4 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.