Triple
T9898328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F# Software Foundation |
E182228
|
entity |
| Predicate | hasCommunityDrivenGovernance |
P91053
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [F# Software Foundation, hasCommunityDrivenGovernance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityDrivenGovernance Context triple: [F# Software Foundation, hasCommunityDrivenGovernance, true]
-
A.
governedCommunity
Indicates that one entity exercises governing authority or administrative control over a community or group of people.
-
B.
developedInCommunity
Indicates that something was created, built, or advanced through the participation, collaboration, or support of a particular community.
-
C.
hasCommunityCouncil
Indicates that an entity is governed, represented, or overseen by a community council.
-
D.
governanceDiffersFrom
Indicates that the form, structure, or style of governance of one entity is different from that of another entity.
-
E.
hasCommunityAspect
Indicates that something involves, reflects, or contributes to a shared community dimension, such as collective participation, interaction, or benefit.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4ac27d88190b8255f7e616f95c9 |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:40 p.m.