Triple
T28421791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian non-free component |
E719957
|
entity |
| Predicate | relationshipToMain |
P201537
|
FINISHED |
| Object | outside Debian main archive |
—
|
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: outside Debian main archive | Statement: [Debian non-free component, relationshipToMain, outside Debian main archive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToMain Context triple: [Debian non-free component, relationshipToMain, outside Debian main archive]
-
A.
relationshipToParent
Indicates the specific familial or social role an entity has in relation to its parent entity.
-
B.
relationshipToMaster
Indicates the type or nature of a subject’s connection, role, or association with a designated master entity.
-
C.
relationshipToParents
Indicates the type or nature of a person's familial relationship to their parents.
-
D.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
E.
relationshipToBond
Indicates the specific type of personal, familial, or professional relationship an entity has to the person named Bond.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
| PDg | Predicate description generation | batch_6a00037aff7c8190940bd1b02cec8c57 |
completed | May 10, 2026, 4:03 a.m. |
Created at: April 28, 2026, 1:34 a.m.