Triple
T18979581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haenyeo female divers |
E464383
|
entity |
| Predicate | harvests |
P38314
|
FINISHED |
| Object | abalone |
—
|
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: abalone | Statement: [Haenyeo female divers, harvests, abalone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harvests Context triple: [Haenyeo female divers, harvests, abalone]
-
A.
harvestPart
Indicates that one entity is a component or portion that is removed or collected from another entity during a harvesting process.
-
B.
isHarvestedBy
chosen
Indicates that something (typically a resource, crop, or material) is collected or gathered through the actions of a particular agent or method.
-
C.
harvestFestival
Indicates a relationship where a community or group holds a celebratory event or ritual to mark and give thanks for the gathering of crops or agricultural produce.
-
D.
harvestCondition
Indicates the specific circumstances or criteria under which a harvest may or should be carried out.
-
E.
hauls
Indicates that one entity pulls, drags, or transports another entity, typically involving effort or force over a distance.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d65b573881908575e61a62b70787 |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.