Triple
T34506418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zambian Jews |
E885898
|
entity |
| Predicate | interactionsWith |
P3970
|
FINISHED |
| Object | wider Zambian society |
—
|
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: wider Zambian society | Statement: [Zambian Jews, interactionsWith, wider Zambian society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionsWith Context triple: [Zambian Jews, interactionsWith, wider Zambian society]
-
A.
interactionBetween
Indicates a reciprocal or mutual action, influence, or communication occurring between two or more entities.
-
B.
specifiesInteractionWith
Indicates that one entity defines or determines the type, parameters, or nature of interaction it has with another entity.
-
C.
interactionWithHumans
Indicates a relationship where an entity engages in some form of contact, communication, or mutual influence with humans.
-
D.
hasInteraction
chosen
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
E.
intendedAudienceInteraction
Indicates that one entity is the target group or audience with whom another entity is meant to interact or engage.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 1, 2026, 2:01 a.m.