Triple
T29689539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gNewSense |
E751176
|
entity |
| Predicate | laterBasedOn |
P197412
|
FINISHED |
| Object | Debian |
—
|
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: Debian | Statement: [gNewSense, laterBasedOn, Debian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBasedOn Context triple: [gNewSense, laterBasedOn, Debian]
-
A.
laterBase
Indicates that one event, state, or version occurs or is valid at a later time than another referenced event, state, or version.
-
B.
basedInLater
Indicates that an entity is located or headquartered in a place during a later time period or phase, relative to some earlier location or state.
-
C.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
D.
laterWithin
Indicates that one event or time point occurs later than another while still falling within a specified temporal interval or boundary.
-
E.
laterExtendedIn
Indicates that an existing entity (such as a work, version, or specification) was subsequently expanded, updated, or built upon by a later entity.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
| PDg | Predicate description generation | batch_69fe9137730c81909d1d57c30566c89a |
completed | May 9, 2026, 1:43 a.m. |
Created at: April 28, 2026, 7:15 p.m.