Triple
T29689560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gNewSense |
E751176
|
entity |
| Predicate | upstream |
P168011
|
FINISHED |
| Object | Debian GNU/Linux |
—
|
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 GNU/Linux | Statement: [gNewSense, upstream, Debian GNU/Linux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upstream Context triple: [gNewSense, upstream, Debian GNU/Linux]
-
A.
upstreamFrom
Indicates that one entity is located or occurs earlier in the flow or sequence relative to another, typically in a direction opposite to the main movement or progression.
-
B.
upstreamRiver
Indicates that one river is located or flows in an upstream direction relative to another river within the same watercourse system.
-
C.
upstreamDam
Indicates that one entity is located or positioned upstream of another entity in relation to a dam, typically affecting or influenced by the dam’s presence or operation.
-
D.
upstreamCity
Indicates that one city is located upstream along a river or waterway relative to another city.
-
E.
upstreamControlledBy
Indicates that the state, behavior, or output of one entity is determined or constrained by another entity that is positioned earlier or higher in a dependency or process flow.
- 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_69f672938e18819082394196f97e6340 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 7:15 p.m.