Triple
T11851866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midsayap |
E281926
|
entity |
| Predicate | hasMajorLivelihood |
P29524
|
FINISHED |
| Object | farming |
—
|
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: farming | Statement: [Midsayap, hasMajorLivelihood, farming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorLivelihood Context triple: [Midsayap, hasMajorLivelihood, farming]
-
A.
livelihood
chosen
Indicates that one entity serves as the primary means of support, income, or subsistence for another entity.
-
B.
livelihoodChange
Indicates a change in a person’s or group’s means of making a living, such as improvements, declines, or shifts in income-generating activities.
-
C.
hasRuralEconomySector
Indicates that an entity participates in, contains, or is associated with an economic sector based on rural activities or rural development.
-
D.
hasMajorEmployer
Indicates that an entity has a primary or most significant employer with which it is chiefly affiliated for work or occupation.
-
E.
hasMainEconomicUse
Indicates that something serves as the primary or principal economic function, purpose, or use of another entity.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a696ee548190800d56c64c339b10 |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.