Triple
T36021641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DBR-1 |
E1042003
|
entity |
| Predicate | hasReportingNameFormat |
—
|
GENERATED |
| Object | alphanumeric code |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReportingNameFormat Context triple: [DBR-1, hasReportingNameFormat, alphanumeric code]
-
A.
hasReportingNameType
Indicates that an entity is associated with a specific type or category of reporting name used to identify it in reports or documentation.
-
B.
hasReportingMarkFormat
chosen
Indicates that one entity’s reporting mark follows or conforms to the specified format or pattern defined by the other entity.
-
C.
usedAsReportingNameDuring
Indicates that one entity functioned as the reporting name or callsign for another entity during a specified time period.
-
D.
hasConfigurationFormat
Indicates that an entity uses or is associated with a specific configuration format for its settings or parameters.
-
E.
hasHumanFormName
Indicates that an entity’s human form is known by a specific name.
- F. None of above.
Provenance (1 batch)
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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.