Triple
T4147247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabine language |
E89813
|
entity |
| Predicate | statusInCorpus |
P127
|
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: [Sabine language, statusInCorpus, poorly attested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInCorpus Context triple: [Sabine language, statusInCorpus, poorly attested]
-
A.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
authorshipStatus
Indicates the current state or condition of an entity’s role as an author in relation to a work (e.g., confirmed, disputed, anonymous, or pending).
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
statusWordRegister
Indicates the level of formality or social register associated with a status-related word in language use.
-
E.
publicationStatus
Indicates the current state or phase of a work within its publication lifecycle, such as draft, under review, published, or retired.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.