Triple
T848995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPT-2 |
E18339
|
entity |
| Predicate | initialReleasePolicy |
P172
|
FINISHED |
| Object | staged release |
—
|
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: staged release | Statement: [GPT-2, initialReleasePolicy, staged release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialReleasePolicy Context triple: [GPT-2, initialReleasePolicy, staged release]
-
A.
initialReleaseWith
Indicates that two or more entities were first released together as part of the same initial release event or package.
-
B.
firstReleaseVersion
Indicates the specific version identifier associated with the initial public release of something.
-
C.
publicRelease
Indicates that something is made available to the general public, typically after any private or restricted access period has ended.
-
D.
implementedPolicy
chosen
Indicates that a particular policy has been put into effect or carried out by an entity.
-
E.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac1fac3481909cba7070ce31a9b3 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa807adc8190ad808a573cf8e923 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.