Triple
T26822188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rice Research Station, Ambasamudram |
E675275
|
entity |
| Predicate | mainCropStudied |
P54821
|
FINISHED |
| Object | Oryza sativa |
—
|
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: Oryza sativa | Statement: [Rice Research Station, Ambasamudram, mainCropStudied, Oryza sativa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCropStudied Context triple: [Rice Research Station, Ambasamudram, mainCropStudied, Oryza sativa]
-
A.
hasCropSpecies
chosen
Indicates that a particular location, field, or agricultural system is associated with or used to cultivate a specified crop species.
-
B.
majorCrop
Indicates that a particular crop is one of the primary or most important crops cultivated in a given area or context.
-
C.
cultivatedSpecies
Indicates that one entity is a species that is intentionally grown or cultivated by another entity.
-
D.
introducedCrop
Indicates that an entity brought a crop species into a new area or context where it was not previously present or cultivated.
-
E.
relatedCrop
Indicates that one crop has a meaningful association with another crop, such as complementary growth, rotation suitability, or shared characteristics.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 4:56 a.m.