Triple
T21805575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US9497461015 |
E538340
|
entity |
| Predicate | hasIssueDate |
P32435
|
FINISHED |
| Object | Unknown |
—
|
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: Unknown | Statement: [US9497461015, hasIssueDate, Unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIssueDate Context triple: [US9497461015, hasIssueDate, Unknown]
-
A.
isIssued
Indicates that an authoritative source formally provides, distributes, or makes something (such as a document, order, or item) officially available to a recipient.
-
B.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another entity.
-
C.
yearOfIssue
Indicates the specific calendar year in which something (such as a document, publication, or item) was formally issued or released.
-
D.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
E.
issuedDocumentDate
chosen
Indicates the date on which a document was formally created, released, or made officially valid by the issuing party.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07802bffc8190b383a2c89de75f74 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.