Triple
T28421794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian non-free component |
E719957
|
entity |
| Predicate | mirroredOn |
P164710
|
FINISHED |
| Object | official Debian mirrors |
—
|
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: official Debian mirrors | Statement: [Debian non-free component, mirroredOn, official Debian mirrors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mirroredOn Context triple: [Debian non-free component, mirroredOn, official Debian mirrors]
-
A.
mirroredAt
Indicates that one entity is a mirror image or reflection of another entity with respect to a specified axis, plane, or point.
-
B.
mirroredBy
Indicates that one entity serves as a reflective counterpart or reversed representation of another.
-
C.
mirrorType
Indicates that one entity is a specific kind or category of mirror in relation to another entity.
-
D.
primaryMirrorShape
Indicates that one entity has a primary mirror whose geometric shape or curvature type is specified by the other entity.
-
E.
trialMirrors
Indicates that one trial serves as a mirror or counterpart to another trial, reflecting its conditions, structure, or outcomes for comparison or replication purposes.
- 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_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 28, 2026, 1:34 a.m.