Triple
T13367635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abjad |
E318980
|
entity |
| Predicate | termIntroductionField |
P109641
|
FINISHED |
| Object | writing system typology |
—
|
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: writing system typology | Statement: [Abjad, termIntroductionField, writing system typology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termIntroductionField Context triple: [Abjad, termIntroductionField, writing system typology]
-
A.
termType
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
-
B.
keyTerm
Indicates that a term functions as a primary or central concept within a given context or information structure.
-
C.
termAlsoUsedFor
Indicates that one term is also used to refer to the same or closely related concept as another term.
-
D.
fieldIntroduced
Indicates that a particular field or attribute was newly added or introduced into a data structure, schema, or record.
-
E.
languageTerm
Indicates that one entity is a linguistic expression (word, phrase, or term) used to denote or label the other entity.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd652d48190a782fd1f57f34b6a |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:32 p.m.