Triple
T9273618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vestinian language |
E222889
|
entity |
| Predicate | attestationStatus |
P66090
|
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: [Vestinian language, attestationStatus, poorly attested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attestationStatus Context triple: [Vestinian language, attestationStatus, poorly attested]
-
A.
attestation
Indicates a formal declaration or confirmation that something is true, accurate, or has been verified.
-
B.
hasAttestation
Indicates that there exists a formal confirmation, evidence, or certification supporting the validity or authenticity of something.
-
C.
timeOfAttestation
Indicates the specific time at which a statement, document, or claim is formally attested or verified.
-
D.
degreeOfAttestation
chosen
Indicates the extent or level to which something (such as a claim, form, or document) is supported, verified, or confirmed by evidence or authoritative sources.
-
E.
alsoAttestedIn
Indicates that the same item, fact, or phenomenon is recorded or evidenced in another source, context, or location as well.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0788e87c81909ccda40d94cc6705 |
completed | April 1, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.