Triple
T33029020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | comp.lang.c |
E845113
|
entity |
| Predicate | relatedNewsgroup |
—
|
GENERATED |
| Object | comp.lang.c.moderated |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedNewsgroup Context triple: [comp.lang.c, relatedNewsgroup, comp.lang.c.moderated]
-
A.
relatedCorrespondence
Indicates that there exists a piece of correspondence (such as a letter, email, or message) that is associated with or pertains to the related entity.
-
B.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
C.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
D.
relatedIntermediate
Indicates an indirect or intermediate relationship between two entities, typically via one or more other entities or steps rather than a direct connection.
-
E.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
- F. None of above.
Provenance (1 batch)
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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:24 a.m.