Triple
T17466186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guinean mangroves |
E425282
|
entity |
| Predicate | supportHumanActivity |
P2186
|
FINISHED |
| Object | small-scale fisheries |
—
|
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: small-scale fisheries | Statement: [Guinean mangroves, supportHumanActivity, small-scale fisheries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportHumanActivity Context triple: [Guinean mangroves, supportHumanActivity, small-scale fisheries]
-
A.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
B.
supportsActivity
chosen
Indicates that one entity provides the necessary conditions, resources, or environment for another entity’s activity to occur or be sustained.
-
C.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
-
D.
addressingSupport
Indicates that one entity provides assistance or resources to help another entity address or resolve a specific issue, need, or challenge.
-
E.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a7e2a481908c32defa3401f848 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.