Triple
T33864552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linux Capital Group |
E868010
|
entity |
| Predicate | associatedPersonRoleOfBruce Perens |
P134996
|
FINISHED |
| Object | open-source advocate |
—
|
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: open-source advocate | Statement: [Linux Capital Group, associatedPersonRoleOfBruce Perens, open-source advocate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPersonRoleOfBruce Perens Context triple: [Linux Capital Group, associatedPersonRoleOfBruce Perens, open-source advocate]
-
A.
associatedPersonField
chosen
Indicates that there is a person linked or connected to the subject in a relevant or contextual way.
-
B.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
C.
namedPersonAssociation
Indicates a relationship where one entity is associated with or identified by a specific personal name.
-
D.
organizationAuthor
Indicates that an organization is the creator or author of a work, document, or resource.
-
E.
namedIndividual
Indicates that the subject is a specific, uniquely identified individual entity rather than a general class or type.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:47 a.m.