Triple
T13241704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAN bus |
E315294
|
entity |
| Predicate | standardIdentifierLength |
P33158
|
FINISHED |
| Object | 11-bit identifier |
—
|
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: 11-bit identifier | Statement: [CAN bus, standardIdentifierLength, 11-bit identifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardIdentifierLength Context triple: [CAN bus, standardIdentifierLength, 11-bit identifier]
-
A.
identifierLength
chosen
Indicates the length or number of characters in an entity’s identifier.
-
B.
standardNumberStandardizedBy
Indicates that a standard number has been formally defined, approved, or regulated by a specific standardizing authority or organization.
-
C.
standardNumber
Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
-
D.
standardIdentity
Indicates that two entities are considered equivalent or identical according to a defined standard or canonical form.
-
E.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d59e84c8190a9e547d0fe26a5f9 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.