Triple
T8246930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ian Murdock |
E192871
|
entity |
| Predicate | inceptionOfDebian |
P81170
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Ian Murdock, inceptionOfDebian, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionOfDebian Context triple: [Ian Murdock, inceptionOfDebian, 1993]
-
A.
initialReleaseApprox
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.
-
B.
firstDeployed
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
-
C.
firstDeployedAt
Indicates the date and time when an entity was initially put into use or made operational.
-
D.
firstDeveloped
Indicates that one entity was the earliest to create, originate, or bring another entity into existence.
-
E.
developedSince
Indicates that something has been created, expanded, or advanced starting from a specified point in time and continuing thereafter.
- F. None of above. chosen
Provenance (4 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb787414508190a08cf47d1545ce50 |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb447c146081909decf97bbd26c496 |
completed | March 31, 2026, 3:50 a.m. |
Created at: March 30, 2026, 5:48 p.m.