Triple
T815846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rust |
E17650
|
entity |
| Predicate | stableReleaseDate |
P9407
|
FINISHED |
| Object | 2015-05-15 |
—
|
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: 2015-05-15 | Statement: [Rust, stableReleaseDate, 2015-05-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stableReleaseDate Context triple: [Rust, stableReleaseDate, 2015-05-15]
-
A.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
B.
latestReleaseDate
chosen
Indicates the date on which the most recent version or release of an entity became available.
-
C.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
-
D.
digitalReleaseDate
Indicates the date on which a work is first made available in digital form (e.g., online or as a digital file).
-
E.
finalReleaseYear
Indicates the calendar year in which something (such as a product, work, or version) is officially released for the last time.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab5157b08190b6c8f2fd455f261e |
completed | March 1, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69a4aa756920819080ae82948974c876 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.