Triple
T9532048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Misgurnus anguillicaudatus |
E229918
|
entity |
| Predicate | aquacultureUse |
P72915
|
FINISHED |
| Object | food fish |
—
|
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: food fish | Statement: [Misgurnus anguillicaudatus, aquacultureUse, food fish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aquacultureUse Context triple: [Misgurnus anguillicaudatus, aquacultureUse, food fish]
-
A.
aquacultureAdvantage
Indicates that engaging in aquaculture provides a benefit, improvement, or positive outcome relative to some alternative or baseline.
-
B.
aquacultureImportance
Indicates the degree to which aquaculture plays a significant or critical role in or has impact on a given entity, system, or context.
-
C.
aquacultureProduct
chosen
Indicates that something is a product derived from aquaculture activities, such as the farming or cultivation of aquatic organisms.
-
D.
agricultureUse
Indicates that something is used for, involved in, or designated for agricultural activities or purposes.
-
E.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
- 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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98b5651881908241b040f123c6a8 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8 p.m.