Triple
T29690052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gNewSense |
E751187
|
entity |
| Predicate | finalReleaseCodename |
P177237
|
FINISHED |
| Object | Ucclia |
—
|
NE NERFINISHED |
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: Ucclia | Statement: [gNewSense, finalReleaseCodename, Ucclia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalReleaseCodename Context triple: [gNewSense, finalReleaseCodename, Ucclia]
-
A.
latestMajorVersionCodeName
chosen
Indicates that one entity is the code name assigned to the most recent major version of another entity (such as a product, software, or system).
-
B.
successorCodename
Indicates that one codename directly follows and replaces another in a sequence or lifecycle.
-
C.
relatedCodename
Indicates that one entity has an associated or connected codename that is contextually related to it.
-
D.
unstableCodename
Indicates that the codename assigned to something is temporary, experimental, or subject to change and should not be relied on as final.
-
E.
releaseName
Indicates that an entity is identified or labeled by a specific release name (e.g., version or edition title).
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 28, 2026, 7:16 p.m.