Triple
T11656883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joost |
E277031
|
entity |
| Predicate | betaRelease |
P40427
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Joost, betaRelease, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: betaRelease Context triple: [Joost, betaRelease, 2007]
-
A.
betaReleaseDate
chosen
Indicates the date on which a product or system is first released in its beta version for testing or limited use.
-
B.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
-
C.
publicRelease
Indicates that something is made available to the general public, typically after any private or restricted access period has ended.
-
D.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
-
E.
targetRelease
Indicates the specific release or version that an item (such as a feature, fix, or component) is planned or designated to be delivered in.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d0331481909682b2e504e4c9a0 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.