Triple
T14993930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | @aoc |
E373906
|
entity |
| Predicate | hasVerificationStatus |
P44723
|
FINISHED |
| Object | likely 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: likely verified account | Statement: [@aoc, hasVerificationStatus, likely verified account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVerificationStatus Context triple: [@aoc, hasVerificationStatus, likely verified account]
-
A.
verificationStatus
chosen
Indicates whether an entity, claim, or item has been checked and confirmed as authentic, accurate, or compliant according to a defined verification process.
-
B.
hasVerifiedOwner
Indicates that an entity is owned by another entity whose ownership status has been confirmed as authentic or legitimate.
-
C.
dataTypeVerified
Indicates that the data’s type has been checked and confirmed to match the expected or required type.
-
D.
identityStatus
Indicates the current state or condition of an entity’s identity, such as whether it is verified, active, pending, or otherwise classified.
-
E.
registrationStatus
Indicates the current state or condition of an entity’s enrollment or registration within a given system or process.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded716ebb481908224d2d4f7561b03 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.