Triple
T666665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States passport |
E12878
|
entity |
| Predicate | issuedTo |
P1695
|
FINISHED |
| Object | United States citizens |
—
|
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: United States citizens | Statement: [United States passport, issuedTo, United States citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuedTo Context triple: [United States passport, issuedTo, United States citizens]
-
A.
issuedBy
Indicates that something (such as a document, order, or statement) has been formally created, authorized, or released by a particular agent or authority.
-
B.
issuedWith
Indicates that one entity is formally provided, granted, or supplied together with another entity as part of the same issuance event.
-
C.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
D.
issuedDocument
chosen
Indicates that one entity has formally created and provided an official document to another entity.
-
E.
presentedTo
Indicates that something (such as an item, work, or information) was formally given, shown, or introduced by one party to another as the recipient.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ff7ca788190bef58ce46849b9d0 |
completed | March 1, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69a49d16cff881908c8d2c3fe4d1d6fb |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.