Triple
T13114471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mundugumor society |
E311057
|
entity |
| Predicate | socialRelations |
P108117
|
FINISHED |
| Object | highly aggressive |
—
|
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: highly aggressive | Statement: [Mundugumor society, socialRelations, highly aggressive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialRelations Context triple: [Mundugumor society, socialRelations, highly aggressive]
-
A.
socialSystem
Indicates a relationship where entities are organized into a structured set of social roles, norms, and interactions that govern their collective behavior.
-
B.
socialComposition
Indicates the makeup or distribution of different social groups or categories within a population or community.
-
C.
socialCircle
Indicates that one entity belongs to, or is part of, the group of people with whom another entity regularly interacts socially.
-
D.
playerRelations
Indicates the nature or status of the relationship between players, such as alliances, rivalries, or other interpersonal dynamics.
-
E.
socialFeature
Indicates that one entity provides or participates in a social interaction capability or function involving other entities.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d98134df64819084a5674f9475dcc2 |
completed | April 10, 2026, 11:01 p.m. |
Created at: April 9, 2026, 9:06 p.m.