Triple
T36021641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DBR-1 |
E1042003
|
entity |
| Predicate | hasReportingNameFormat |
P168013
|
FINISHED |
| Object | alphanumeric code |
—
|
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: alphanumeric code | Statement: [DBR-1, hasReportingNameFormat, alphanumeric code]
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 (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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.