Triple
T9057858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marlene (Marlene) |
E217048
|
entity |
| Predicate | identificationStatus |
P30421
|
FINISHED |
| Object | uncertain |
—
|
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: uncertain | Statement: [Marlene (Marlene), identificationStatus, uncertain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identificationStatus Context triple: [Marlene (Marlene), identificationStatus, uncertain]
-
A.
identityStatus
chosen
Indicates the current state or condition of an entity’s identity, such as whether it is verified, active, pending, or otherwise classified.
-
B.
identificationType
Indicates the specific kind or category of identification associated with an entity or relationship.
-
C.
designationStatus
Indicates the current official classification or standing assigned to an entity within a defined system or process.
-
D.
registrationStatus
Indicates the current state or condition of an entity’s enrollment or registration within a given system or process.
-
E.
recognitionStatus
Indicates the current state or outcome of acknowledging, validating, or officially accepting something or someone.
- 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_69ca83d4425481909a319dab847724ec |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7ec808bc8190957b80820d98fd5b |
completed | April 1, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee6d83c819095d8ed0779aa8511 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:10 p.m.