Triple
T8285048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linux kernel community |
E193768
|
entity |
| Predicate | usesDevelopmentModel |
P24782
|
FINISHED |
| Object | bazaar model |
—
|
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: bazaar model | Statement: [Linux kernel community, usesDevelopmentModel, bazaar model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDevelopmentModel Context triple: [Linux kernel community, usesDevelopmentModel, bazaar model]
-
A.
usesProductionModel
Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
-
B.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
C.
hasDevelopmentSystem
chosen
Indicates that one entity possesses, uses, or is associated with a particular system, platform, or environment used for development activities.
-
D.
hasDevelopmentStatus
Indicates the current stage or condition of progress or completion that something is in.
-
E.
mainDevelopmentPeriod
Indicates the primary time span during which the main development or formation of something took place.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad20ae481908179aba245c73fad |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:52 p.m.