Triple
T26074175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adams catalyst |
E657633
|
entity |
| Predicate | hasRegistryNumber |
P41462
|
FINISHED |
| Object | CAS 1314-15-4 |
—
|
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: CAS 1314-15-4 | Statement: [Adams catalyst, hasRegistryNumber, CAS 1314-15-4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegistryNumber Context triple: [Adams catalyst, hasRegistryNumber, CAS 1314-15-4]
-
A.
registrationNumber
chosen
Indicates the unique identifier assigned to an entity as part of an official or formal registration process.
-
B.
regulationNumber
Indicates the specific identifier or code assigned to a regulation that governs or constrains an entity or activity.
-
C.
hasCarNumberPreviously
Indicates that an entity has been associated with a specific car number at some earlier time before the current context.
-
D.
notableVehicleNumber
Indicates that a specific vehicle is identified as notable or significant by a particular number or identifier.
-
E.
hasRegimentNumber
Indicates that an entity (such as a military unit) is assigned a specific regiment number as its identifying designation.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 26, 2026, 7:32 p.m.