Triple
T6991601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan 9 from Bell Labs |
E162097
|
entity |
| Predicate | initialRelease |
P56255
|
FINISHED |
| Object | early 1990s |
—
|
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: early 1990s | Statement: [Plan 9 from Bell Labs, initialRelease, early 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialRelease Context triple: [Plan 9 from Bell Labs, initialRelease, early 1990s]
-
A.
initialReleaseWith
Indicates that two or more entities were first released together as part of the same initial release event or package.
-
B.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
C.
initialReleaseApprox
chosen
Indicates that an entity’s first release or debut occurred around an estimated or approximate point in time rather than on a precisely known date.
-
D.
firstReleaseVersion
Indicates the specific version identifier associated with the initial public release of something.
-
E.
firstReleaseEvent
Indicates the event at which something (typically a creative work or product) was first officially released.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc1f63c8190837cfd71cf5ed613 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.