Triple
T10332610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cm |
E242913
|
entity |
| Predicate | hasNotationStyle |
P1609
|
FINISHED |
| Object | prefix followed by serial number (e.g. Cm 1234) |
—
|
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: prefix followed by serial number (e.g. Cm 1234) | Statement: [Cm, hasNotationStyle, prefix followed by serial number (e.g. Cm 1234)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotationStyle Context triple: [Cm, hasNotationStyle, prefix followed by serial number (e.g. Cm 1234)]
-
A.
hasStructuralStyle
Indicates that one entity possesses, exhibits, or is characterized by a particular architectural or structural design style.
-
B.
hasObjectNotation
Indicates that an entity is represented or expressed using a specific object-based notation or symbolic format.
-
C.
hasStyle
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
D.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
E.
distinguishingNotation
Indicates that one entity uses a specific notation or symbol to distinguish or differentiate another entity from similar ones.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:53 a.m.