Triple
T13114430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arapesh society |
E311056
|
entity |
| Predicate | socialValues |
P21593
|
FINISHED |
| Object | cooperation |
—
|
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: cooperation | Statement: [Arapesh society, socialValues, cooperation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialValues Context triple: [Arapesh society, socialValues, cooperation]
-
A.
socialImpact
Indicates the extent to which an action, entity, or relationship affects society or communities, whether positively or negatively.
-
B.
socialContribution
chosen
Indicates that an entity engages in actions or provides resources that benefit society or a community beyond its own direct interests.
-
C.
socialConcern
Indicates a relationship where an entity is concerned about, attentive to, or actively engaged with social issues, problems, or well-being.
-
D.
socialIssue
Indicates a relationship where something is recognized or treated as a problem or concern affecting society or a community at large.
-
E.
philanthropicGoal
Indicates a relationship where an action, initiative, or entity is directed toward achieving a charitable or socially beneficial objective.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98180b6ac8190ae5a1f7c1480bd54 |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.