Triple
T3503590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester encoding |
E74022
|
entity |
| Predicate | encodingRule |
P15447
|
FINISHED |
| Object | each bit period contains at least one transition |
—
|
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: each bit period contains at least one transition | Statement: [Manchester encoding, encodingRule, each bit period contains at least one transition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encodingRule Context triple: [Manchester encoding, encodingRule, each bit period contains at least one transition]
-
A.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
-
B.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
C.
protocolRule
chosen
Indicates that a specified rule or constraint governs how a protocol should be used, structured, or executed between entities.
-
D.
encodingScope
Indicates the range or extent of content or information that is covered, represented, or captured by a particular encoding.
-
E.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf0c2b48190b49923137bb9e45d |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.