Triple
T23927831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | therealdebramessing |
E602406
|
entity |
| Predicate | hasVerifiedStatus |
P44723
|
FINISHED |
| Object | likely true |
—
|
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 true | Statement: [therealdebramessing, hasVerifiedStatus, likely true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVerifiedStatus Context triple: [therealdebramessing, hasVerifiedStatus, likely true]
-
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.
securedStatus
Indicates that an entity’s state, access, or data has been protected or locked down to prevent unauthorized use or modification.
-
E.
trustedStatus
Indicates that one entity regards another as reliable, dependable, or worthy of confidence in a given context.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1efb348190b4cbb32b3b6c9ae4 |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:49 p.m.