Triple
T3426324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Chromium Project |
E72236
|
entity |
| Predicate | acceptsContributionsFrom |
P30146
|
FINISHED |
| Object | external developers |
—
|
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: external developers | Statement: [The Chromium Project, acceptsContributionsFrom, external developers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsContributionsFrom Context triple: [The Chromium Project, acceptsContributionsFrom, external developers]
-
A.
hasContributionFrom
chosen
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
B.
tributeFrom
Indicates that one entity pays or provides tribute, often as a sign of submission or obligation, to another entity.
-
C.
tributeMethod
Indicates the means or manner by which tribute is given, delivered, or fulfilled between parties.
-
D.
tributeSystem
Indicates a relationship where one entity regularly provides payments, goods, or services to another as a sign of submission, allegiance, or obligation.
-
E.
philanthropicBeneficiary
Indicates that one entity is the recipient or target of another entity’s philanthropic giving or charitable support.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9812a648190ac919e7291744b5a |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.