Triple
T6195921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khwāja |
E138507
|
entity |
| Predicate | etymologicalRole |
P69596
|
FINISHED |
| Object | title preceding personal name |
—
|
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: title preceding personal name | Statement: [Khwāja, etymologicalRole, title preceding personal name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologicalRole Context triple: [Khwāja, etymologicalRole, title preceding personal name]
-
A.
etymologicalField
Indicates that one term belongs to a particular semantic or conceptual domain relevant to its etymological origin or historical development.
-
B.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
C.
etymologicalForm
Indicates that one linguistic form is derived from, or historically originates in, another form as its etymological source.
-
D.
etymologicalNote
Indicates that there is a note explaining the origin, historical development, or source language of a term or name.
-
E.
etymologicalSource
Indicates that one term or name originates from, is derived from, or has its roots in another term or name.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0624571508190bd273b4a051fbe41 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:20 p.m.