Triple
T38309534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regor (cut-down) |
E1033645
|
entity |
| Predicate | isDieHarvestedVariantOf |
P190631
|
FINISHED |
| Object | Regor |
—
|
NE NERFINISHED |
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: Regor | Statement: [Regor (cut-down), isDieHarvestedVariantOf, Regor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDieHarvestedVariantOf Context triple: [Regor (cut-down), isDieHarvestedVariantOf, Regor]
-
A.
isRepresentativeVarietyOf
Indicates that one entity serves as a typical or standard example representing the broader characteristics of another entity or group.
-
B.
isHarvestedBy
Indicates that something (typically a resource, crop, or material) is collected or gathered through the actions of a particular agent or method.
-
C.
isPrimaryVarietyOf
Indicates that one variety is the main or principal form of another related variety or entity.
-
D.
isInlandVarietyOf
Indicates that one entity is a variety or subtype of another that occurs specifically in inland (non-coastal) areas.
-
E.
isTypicallyHarvested
Indicates that an entity is commonly gathered or collected, usually at a particular time or stage, for use or consumption.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:30 p.m.