Triple
T2489242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romani organizations |
E51999
|
entity |
| Predicate | oftenLedBy |
P35853
|
FINISHED |
| Object | Romani activists |
—
|
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: Romani activists | Statement: [Romani organizations, oftenLedBy, Romani activists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenLedBy Context triple: [Romani organizations, oftenLedBy, Romani activists]
-
A.
leadingOrgan
Indicates that one entity serves as the primary or most responsible organizing body or authority for another entity or activity.
-
B.
organizationLed
Indicates that one organization provides leadership, direction, or governance over another organization or collective effort.
-
C.
hadLeadershipFrom
chosen
Indicates that one entity received leadership, guidance, or direction from another entity.
-
D.
facilitatedBy
Indicates that an action, process, or relationship occurs or is made easier through the assistance, support, or enabling role of a particular agent or mechanism.
-
E.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.