Triple
T4325131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Source Initiative |
E96618
|
entity |
| Predicate | nonProfitSector |
P56249
|
FINISHED |
| Object | technology |
—
|
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: technology | Statement: [Open Source Initiative, nonProfitSector, technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonProfitSector Context triple: [Open Source Initiative, nonProfitSector, technology]
-
A.
nonProfitContext
Indicates that the relationship or action occurs within, is associated with, or is specifically relevant to a nonprofit or charitable organizational context.
-
B.
nonprofitType
Indicates the specific category or classification of a nonprofit organization based on its legal or functional type.
-
C.
isNonProfitProjectOf
Indicates that a project operates on a non-profit basis and is initiated, owned, or managed by the referenced entity.
-
D.
fieldOfPhilanthropy
Indicates that an entity is engaged in or associated with a particular area or domain of philanthropic activity.
-
E.
nonprofitStatus
Indicates that an entity operates as a nonprofit organization, typically meeting legal or regulatory criteria for nonprofit status.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3512ec18481908a7b5c29b3902b53 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:13 p.m.