Triple
T17483326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRZ-L |
E425716
|
entity |
| Predicate | relatedStandardConcept |
P111023
|
FINISHED |
| Object | line coding in data communication theory |
—
|
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: line coding in data communication theory | Statement: [NRZ-L, relatedStandardConcept, line coding in data communication theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedStandardConcept Context triple: [NRZ-L, relatedStandardConcept, line coding in data communication theory]
-
A.
definitionOfRelatedConcept
Indicates that one concept provides the formal meaning, explanation, or characterization of another closely related concept.
-
B.
relatedClassification
Indicates a relationship where one classification is associated with, linked to, or otherwise contextually connected to another classification.
-
C.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
D.
relatedToTerm
chosen
Indicates a general, non-specific relationship or association between one term and another.
-
E.
relatedConstant
Indicates that one entity is a fixed, unchanging value or constant that is associated with or linked to another entity.
- F. None of above.
Provenance (3 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d06c2881909632845dd7a6b1e3 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.