Triple
T33248226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Com |
E851162
|
entity |
| Predicate | primaryLivelihoodOfResidents |
P29524
|
FINISHED |
| Object | fishing |
—
|
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: fishing | Statement: [Com, primaryLivelihoodOfResidents, fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLivelihoodOfResidents Context triple: [Com, primaryLivelihoodOfResidents, fishing]
-
A.
livelihood
chosen
Indicates that one entity serves as the primary means of support, income, or subsistence for another entity.
-
B.
livelihoodArea
Indicates the area or domain in which an entity earns its living or sustains its means of support.
-
C.
significantResidentOccupation
Indicates that a resident’s occupation is notably important or defining in the context of their residence or community.
-
D.
primaryLandUse
Indicates the main or dominant way in which a given piece of land is utilized or designated (e.g., residential, agricultural, commercial).
-
E.
householdOccupation
Indicates that an entity’s role, job, or function is specifically associated with work or duties performed within a household.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:31 a.m.