Triple
T30369367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | transition network |
E772507
|
entity |
| Predicate | hasTypicalAlphabet |
P7160
|
FINISHED |
| Object | words |
—
|
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: words | Statement: [transition network, hasTypicalAlphabet, words]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAlphabet Context triple: [transition network, hasTypicalAlphabet, words]
-
A.
usesAlphabet
chosen
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
B.
hasTypicalCharacterType
Indicates that an entity is commonly associated with or exemplified by a particular type of character or persona.
-
C.
hasBasicLetters
Indicates that an entity contains or is composed of fundamental alphabetic characters, without additional symbols or diacritics.
-
D.
hasLatinAlphabetStandard
Indicates that there exists an established standard or convention for representing something using the Latin alphabet.
-
E.
hasTypicalSpelling
Indicates that one form is the standard or commonly accepted spelling of another form.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 29, 2026, 7:59 p.m.