Triple
T418499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consular Report of Birth Abroad |
E8046
|
entity |
| Predicate | appliedForBy |
P11183
|
FINISHED |
| Object | U.S. citizen parent or legal guardian |
—
|
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: U.S. citizen parent or legal guardian | Statement: [Consular Report of Birth Abroad, appliedForBy, U.S. citizen parent or legal guardian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedForBy Context triple: [Consular Report of Birth Abroad, appliedForBy, U.S. citizen parent or legal guardian]
-
A.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
B.
applicantType
Indicates the classification or category of an applicant in relation to an application or selection process.
-
C.
requestedBy
chosen
Indicates that one entity has made a request for something to be done, provided, or obtained by another entity.
-
D.
attendedBy
Indicates that an event, place, or activity is participated in or visited by a particular person or group.
-
E.
appliedBecauseOf
Indicates that one entity is applied, used, or enacted as a consequence or result of another specified cause or condition.
- 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.