Triple
T32271000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian Jews |
E824412
|
entity |
| Predicate | run |
P173906
|
FINISHED |
| Object | Jewish philanthropic organizations |
—
|
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: Jewish philanthropic organizations | Statement: [Brazilian Jews, run, Jewish philanthropic organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: run Context triple: [Brazilian Jews, run, Jewish philanthropic organizations]
-
A.
runs
Indicates that an entity moves swiftly on foot, typically using its legs in a continuous, rapid motion.
-
B.
ranIn
Indicates that an entity performed a running action within or during a specified location, context, or time frame.
-
C.
ranOn
Indicates that an entity executed or operated on a particular platform, system, or environment.
-
D.
ranAs
Indicates that one entity previously operated or functioned in the role, capacity, or identity of another entity.
-
E.
runsFrom
Indicates that one entity flees or escapes away from another entity.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc8766048190a663b878529d5450 |
completed | May 3, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:42 a.m.