Triple
T32515297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4.3BSD |
E831043
|
entity |
| Predicate | developerGroup |
P23778
|
FINISHED |
| Object | CSRG at UC Berkeley |
—
|
NE NERFINISHED |
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: CSRG at UC Berkeley | Statement: [4.3BSD, developerGroup, CSRG at UC Berkeley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerGroup Context triple: [4.3BSD, developerGroup, CSRG at UC Berkeley]
-
A.
developmentTeamFor
chosen
Indicates the team responsible for developing or building a particular product, project, or system.
-
B.
developerStudio
Indicates that a software developer or development team is associated with, works at, or uses a particular development studio or integrated development environment (IDE).
-
C.
platformDeveloper
Indicates that one entity is the developer or creator responsible for building or maintaining the other entity as a platform.
-
D.
developerRenamedTo
Indicates that a developer previously known by one name is now identified by a new name.
-
E.
developmentRole
Indicates that an entity participates in the creation, design, or production of another entity in a specific developmental capacity or function.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1 a.m.