Triple
T33467150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebkay |
E857084
|
entity |
| Predicate | statusOfAttestation |
P190791
|
FINISHED |
| Object | poorly attested |
—
|
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: poorly attested | Statement: [Sebkay, statusOfAttestation, poorly attested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfAttestation Context triple: [Sebkay, statusOfAttestation, poorly attested]
-
A.
hasAttestationStatus
chosen
Indicates the current verification or approval state that has been assigned to something, such as whether it has been formally attested, validated, or certified.
-
B.
hasAttestation
Indicates that there exists a formal confirmation, evidence, or certification supporting the validity or authenticity of something.
-
C.
attestation
Indicates a formal declaration or confirmation that something is true, accurate, or has been verified.
-
D.
certificateStatus
Indicates the current validity or state (e.g., valid, expired, revoked) of a certificate within a given system or context.
-
E.
timeOfAttestation
Indicates the specific time at which a statement, document, or claim is formally attested or verified.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 1, 2026, 1:37 a.m.