Triple
T36083718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRZ |
E1043719
|
entity |
| Predicate | locationOnDocument |
P1637
|
FINISHED |
| Object | data page of passport |
—
|
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: data page of passport | Statement: [MRZ, locationOnDocument, data page of passport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOnDocument Context triple: [MRZ, locationOnDocument, data page of passport]
-
A.
locationInDocument
chosen
Indicates that one entity specifies where another entity is situated or referenced within a document.
-
B.
documentLocation
Indicates the physical or digital place where a document is stored, kept, or can be accessed.
-
C.
locationOnField
Indicates the specific position or area that an entity occupies on a defined field or playing surface.
-
D.
locationOnDevice
Indicates that one entity is stored or situated on a particular device.
-
E.
locationWhenGiven
Indicates the place where an entity is located at the time it is given or transferred to another entity.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.