Triple
T22330972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B38M |
E552019
|
entity |
| Predicate | relatedDesignator |
P103473
|
FINISHED |
| Object | B739 |
—
|
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: B739 | Statement: [B38M, relatedDesignator, B739]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedDesignator Context triple: [B38M, relatedDesignator, B739]
-
A.
designatorType
Indicates the specific role or category of a designator used to identify or reference an entity within a system or context.
-
B.
associatedWithDesignerLabel
Indicates a relationship where something is linked or connected to a particular designer label, typically signifying brand association or attribution.
-
C.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
D.
associatedWithDesign
Indicates that there is a connection or involvement between an entity and a particular design, design process, or design-related activity.
-
E.
usesDesignator
chosen
Indicates that one entity employs or references a specific designator (such as a name, code, or identifier) to denote or refer 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1577a9c348190b8662142afa832be |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.