Triple
T19261603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menkent |
E481660
|
entity |
| Predicate | hasBDNumber |
P133480
|
FINISHED |
| Object | BD−35 9648 |
—
|
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: BD−35 9648 | Statement: [Menkent, hasBDNumber, BD−35 9648]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBDNumber Context triple: [Menkent, hasBDNumber, BD−35 9648]
-
A.
BDNumber
chosen
Indicates that an entity is associated with a specific BD (Business Development or similar domain-specific) identification number used to uniquely reference it.
-
B.
hasIbnr
Indicates that one entity possesses or is associated with an incurred-but-not-reported (IBNR) amount, typically referring to estimated liabilities for events that have occurred but have not yet been reported.
-
C.
hasBandNumber
Indicates that an entity is associated with a specific band identification number.
-
D.
hasNationalIdentity
Indicates that an entity possesses or is associated with a particular national identity or nationality.
-
E.
hasBDDesignation
Indicates that an entity has been assigned a specific BD (Business Development or similar domain-specific) designation or classification.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8a022c8190b313e9d11d38e482 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.