Triple
T26016306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LGBTQ+ organizations |
E647031
|
entity |
| Predicate | oftenCollaborateWith |
P129005
|
FINISHED |
| Object | human rights 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: human rights organizations | Statement: [LGBTQ+ organizations, oftenCollaborateWith, human rights organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenCollaborateWith Context triple: [LGBTQ+ organizations, oftenCollaborateWith, human rights organizations]
-
A.
frequentlyCollaboratedWith
chosen
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
-
B.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
C.
usesCollaboration
Indicates that one entity employs or relies on collaborative methods, tools, or partnerships with another entity to achieve a shared goal or perform an activity.
-
D.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
E.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 22, 2026, 9:03 a.m.