Triple
T31361133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-AJEY |
E799869
|
entity |
| Predicate | civilRegistrationCode |
P171666
|
FINISHED |
| Object | D-AJEY |
—
|
NE NERFINISHED |
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: D-AJEY | Statement: [D-AJEY, civilRegistrationCode, D-AJEY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilRegistrationCode Context triple: [D-AJEY, civilRegistrationCode, D-AJEY]
-
A.
civilRegistrationCodeOf
chosen
Indicates that one entity is the civil registration code assigned to identify another entity in official civil records.
-
B.
civilRegistration
Indicates the official recording of a person’s vital life event (such as birth, marriage, or death) by a civil authority.
-
C.
civilRegistrationCategory
Indicates the specific type or classification of a civil registration event or record associated with an entity.
-
D.
civilRegistrationPrefixExample
Indicates that there is an example of a standard prefix used in civil registration identifiers or records.
-
E.
civilStatus
Indicates the legal marital or family-related status of a person (e.g., single, married, divorced, widowed) at a given time.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:18 p.m.