Triple

T29858107
Position Surface form Disambiguated ID Type / Status
Subject Paraguayan diaspora E758243 entity
Predicate maintainsContactThrough P39803 FINISHED
Object remittances to Paraguay 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: remittances to Paraguay | Statement: [Paraguayan diaspora, maintainsContactThrough, remittances to Paraguay]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maintainsContactThrough
Context triple: [Paraguayan diaspora, maintainsContactThrough, remittances to Paraguay]
  • A. contactWith
    Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
  • B. maintainsThrough chosen
    Indicates that one entity preserves, upholds, or continues a state, condition, or relationship by means of another specified entity, process, or medium.
  • C. worksAsContactFor
    Indicates that one entity serves as the designated contact person or liaison for another entity.
  • D. hasKontakion
    Indicates that an entity is associated with or possesses a specific kontakion, i.e., a particular liturgical hymn or chant.
  • E. maintainedFor
    Indicates that something is kept in a particular state, condition, or operation for the benefit, use, or purpose 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_69f2245b4dec8190b85f664d918a00a5 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f7308a096081909d66a56f3c926806 completed May 3, 2026, 11:24 a.m.
PD Predicate disambiguation batch_69f72a00c5f081908b6539d15baf4e12 completed May 3, 2026, 10:57 a.m.
Created at: April 29, 2026, 5:47 p.m.