Triple
T418521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consular Report of Birth Abroad |
E8046
|
entity |
| Predicate | documentFormat |
P130
|
FINISHED |
| Object | printed certificate |
—
|
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: printed certificate | Statement: [Consular Report of Birth Abroad, documentFormat, printed certificate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentFormat Context triple: [Consular Report of Birth Abroad, documentFormat, printed certificate]
-
A.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
B.
documentModel
Indicates that an entity serves as or is associated with a specific structured representation or schema of a document.
-
C.
documentNumber
Indicates the unique identifying number assigned to a specific document in the relationship.
-
D.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
E.
writtenForm
Indicates that one entity is the textual or orthographic representation (spelling or written version) of 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd1ca148190a66bd8c5aad867d5 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.