Triple
T12724376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banaue Rice Terraces |
E304065
|
entity |
| Predicate | secondaryCrop |
P72116
|
FINISHED |
| Object | vegetables |
—
|
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: vegetables | Statement: [Banaue Rice Terraces, secondaryCrop, vegetables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryCrop Context triple: [Banaue Rice Terraces, secondaryCrop, vegetables]
-
A.
secondaryFood
chosen
Indicates that one entity serves as a secondary or supplementary food source in relation to another entity.
-
B.
majorCrop
Indicates that a particular crop is one of the primary or most important crops cultivated in a given area or context.
-
C.
relatedCrop
Indicates that one crop has a meaningful association with another crop, such as complementary growth, rotation suitability, or shared characteristics.
-
D.
crop
Indicates the action of cutting or trimming part of an object or image, typically to remove unwanted outer areas while keeping a selected region.
-
E.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:25 p.m.