Triple
T18386268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3A |
E446599
|
entity |
| Predicate | designationFormat |
P39478
|
FINISHED |
| Object | numeric with letter suffix |
—
|
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: numeric with letter suffix | Statement: [3A, designationFormat, numeric with letter suffix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designationFormat Context triple: [3A, designationFormat, numeric with letter suffix]
-
A.
designationType
Indicates the specific category or kind of formal status, title, or label that has been assigned in a designation relationship.
-
B.
designationScheme
Indicates the classification or naming system under which an entity’s designations or identifiers are defined.
-
C.
nameStyle
chosen
Indicates how an entity’s name is formatted or stylistically presented (e.g., capitalization, punctuation, or naming convention).
-
D.
designationFor
Indicates that one entity serves as the official title, label, or role name assigned to another entity.
-
E.
designationComponent
Indicates that one entity functions as a component or constituent part of another entity’s designation or formal naming.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e517a00c608190a8f0010c7b53df90 |
completed | April 19, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.