Triple
T12178785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soqotri people |
E290161
|
entity |
| Predicate | traditionalWritingStatus |
P103604
|
FINISHED |
| Object | largely oral tradition |
—
|
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: largely oral tradition | Statement: [Soqotri people, traditionalWritingStatus, largely oral tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalWritingStatus Context triple: [Soqotri people, traditionalWritingStatus, largely oral tradition]
-
A.
writingsStatus
Indicates the status or condition of a set of writings (e.g., whether they are drafted, reviewed, published, or otherwise processed) in relation to an entity.
-
B.
writingSectionStatus
Indicates the current state or progress of a specific writing section within a larger document or workflow.
-
C.
currentlyWrittenIn
Indicates that a work or document is, at the present time, expressed or composed in a particular language or writing system.
-
D.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
-
E.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
- F. None of above. chosen
Provenance (4 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91a83012c81908d04bbab5fdcd8c2 |
completed | April 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69d91510a258819090ef8fbdc2d8707b |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d91a7e0fc081909ec9769231e728a4 |
completed | April 10, 2026, 3:42 p.m. |
Created at: April 8, 2026, 9:50 p.m.