Triple
T418508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consular Report of Birth Abroad |
E8046
|
entity |
| Predicate | validity |
P9768
|
FINISHED |
| Object | does not expire |
—
|
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: does not expire | Statement: [Consular Report of Birth Abroad, validity, does not expire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: validity Context triple: [Consular Report of Birth Abroad, validity, does not expire]
-
A.
validIn
chosen
Indicates that a given entity, statement, or condition is applicable, correct, or legally/semantically acceptable within a specified context, scope, or domain.
-
B.
verdict
Indicates the formal decision or judgment reached and declared at the conclusion of a legal or evaluative process.
-
C.
ability
Indicates that an entity has the capacity or power to perform a particular action or achieve a specific outcome.
-
D.
justification
Indicates that one entity provides a reason, explanation, or supporting argument for the existence, validity, or appropriateness of another entity or claim.
-
E.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
- 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.