Triple
T32417794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNIX Research at UC Berkeley |
E828366
|
entity |
| Predicate | usedUpstreamCodeFrom |
P11905
|
FINISHED |
| Object | AT&T Unix |
—
|
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: AT&T Unix | Statement: [UNIX Research at UC Berkeley, usedUpstreamCodeFrom, AT&T Unix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedUpstreamCodeFrom Context triple: [UNIX Research at UC Berkeley, usedUpstreamCodeFrom, AT&T Unix]
-
A.
upstreamFrom
Indicates that one entity is located or occurs earlier in the flow or sequence relative to another, typically in a direction opposite to the main movement or progression.
-
B.
usesUpstreamProject
chosen
Indicates that one entity depends on, incorporates, or builds upon another entity as an upstream project in its development or operation.
-
C.
usedFromApprox
Indicates that something has been used starting from an approximate point in time or condition, rather than from a precisely defined one.
-
D.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
E.
usedFromLocation
Indicates that something is utilized or operated starting from a specific location.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c27db73c8190b8b90568b70a578b |
completed | May 3, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:54 a.m.