Triple
T15832807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | @dilmabr |
E383911
|
entity |
| Predicate | accountStatus |
P79833
|
FINISHED |
| Object | verified account |
—
|
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: verified account | Statement: [@dilmabr, accountStatus, verified account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accountStatus Context triple: [@dilmabr, accountStatus, verified account]
-
A.
registrationStatus
Indicates the current state or condition of an entity’s enrollment or registration within a given system or process.
-
B.
hasFinancialStatus
Indicates that an entity possesses or is characterized by a particular financial condition, standing, or level of economic well-being.
-
C.
agencyStatus
Indicates the current operational or legal condition under which an agency or agent is functioning (e.g., active, inactive, suspended, or terminated).
-
D.
activationStatus
chosen
Indicates whether an entity is currently active, enabled, or in effect within a given context.
-
E.
bankStatus
Indicates the current operational or financial condition of a bank, such as whether it is active, suspended, solvent, or insolvent.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e653e388190a4696cdb22546715 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.