Triple
T29953531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BR 60800 Green Arrow |
E760833
|
entity |
| Predicate | BRNumber |
P168291
|
FINISHED |
| Object | 60800 |
—
|
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: 60800 | Statement: [BR 60800 Green Arrow, BRNumber, 60800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BRNumber Context triple: [BR 60800 Green Arrow, BRNumber, 60800]
-
A.
BOENumber
Indicates a relationship where an entity is associated with a specific BOE (Bill of Entry) identification number used for customs or import documentation.
-
B.
branchNumber
Indicates the specific branch identifier or code assigned to distinguish one branch from others within the same organization or system.
-
C.
BDNumber
Indicates that an entity is associated with a specific BD (Business Development or similar domain-specific) identification number used to uniquely reference it.
-
D.
issueNumber
Indicates the specific numeric identifier assigned to distinguish one issue from others within a series or collection.
-
E.
ISONumber
Indicates that an entity is associated with, identified by, or conforms to a specific ISO (International Organization for Standardization) number or standard.
- F. None of above. chosen
Provenance (4 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6783880608190906379178b865dc0 |
completed | May 2, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:26 p.m.