Triple
T33029020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | comp.lang.c |
E845113
|
entity |
| Predicate | relatedNewsgroup |
P37
|
FINISHED |
| Object | comp.lang.c.moderated |
E845113
|
NE 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: comp.lang.c.moderated | Statement: [comp.lang.c, relatedNewsgroup, comp.lang.c.moderated]
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 (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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34e50ab1e881908c0be25cab667034 |
completed | June 19, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:24 a.m.