Triple
T666693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States passport |
E12878
|
entity |
| Predicate | travelDocumentNumberFormat |
P17422
|
FINISHED |
| Object | alphanumeric |
—
|
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 | Statement: [United States passport, travelDocumentNumberFormat, alphanumeric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelDocumentNumberFormat Context triple: [United States passport, travelDocumentNumberFormat, alphanumeric]
-
A.
typeOfDocumentIssued
Indicates the specific kind or category of document that has been formally issued in a given context.
-
B.
hasIdentityDocument
Indicates that an entity possesses or is associated with a specific identity document.
-
C.
documentNumber
Indicates the unique identifying number assigned to a specific document in the relationship.
-
D.
formOfRecognition
Indicates a relationship where one entity serves as an official acknowledgment, honor, or validation granted to another entity.
-
E.
visaRequirement
Indicates whether one party must obtain a visa in order to enter, stay in, or transit through the territory of another party.
- 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_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. |
| PDg | Predicate description generation | batch_69a49df19c9481909cc9bc33ed7f011b |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.