Triple
T29585759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1987 Fijian coups d'état |
E754014
|
entity |
| Predicate | effectOnCommunity |
P65945
|
FINISHED |
| Object | marginalization of Indo-Fijian community |
—
|
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: marginalization of Indo-Fijian community | Statement: [1987 Fijian coups d'état, effectOnCommunity, marginalization of Indo-Fijian community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnCommunity Context triple: [1987 Fijian coups d'état, effectOnCommunity, marginalization of Indo-Fijian community]
-
A.
effectOnOthers
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
B.
influencesCommunity
chosen
Indicates that one entity has an effect on the behavior, attitudes, or conditions of a community.
-
C.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
D.
notableCommunityAffected
Indicates that a particular community of notable significance is directly impacted or influenced by the subject.
-
E.
socialImpact
Indicates the extent to which an action, entity, or relationship affects society or communities, whether positively or negatively.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 6:10 p.m.