Triple
T26732389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alawis |
E674007
|
entity |
| Predicate | useText |
P161179
|
FINISHED |
| Object | esoteric religious writings |
—
|
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: esoteric religious writings | Statement: [Alawis, useText, esoteric religious writings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useText Context triple: [Alawis, useText, esoteric religious writings]
-
A.
usesTextBy
Indicates that one entity makes use of or relies on a text authored or provided by another entity.
-
B.
usesTextService
Indicates that an entity makes use of a text-based service to perform some function or obtain some benefit.
-
C.
allowsText
Indicates that one entity permits or supports the use, input, or display of textual content in relation to another entity.
-
D.
textBy
Indicates that a given text or written content was authored or produced by a particular entity.
-
E.
textType
Indicates the classification of a text according to its type, format, or genre.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f618429e9481908140bb49a3edd6de |
completed | May 2, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 3:45 a.m.