Triple
T6352116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faroese |
E142895
|
entity |
| Predicate | writingStandardizedInCentury |
P4436
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Faroese, writingStandardizedInCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingStandardizedInCentury Context triple: [Faroese, writingStandardizedInCentury, 19th century]
-
A.
standardizedInCentury
chosen
Indicates that something was standardized or formally established according to a common norm during a specified century.
-
B.
convertedInCentury
Indicates that an entity underwent a conversion (e.g., religious, functional, or status change) during a specified century.
-
C.
formedInCentury
Indicates that an entity (such as an organization, group, or structure) was established or came into existence during a specified century.
-
D.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
E.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
- 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_69c008d6dcbc8190aa1c2f1fd8916b42 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067dd3c74819085a164b750094c46 |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.