Triple
T31344280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UP24 |
E799398
|
entity |
| Predicate | languageOfPrefix |
P99563
|
FINISHED |
| Object | English alphabet |
—
|
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: English alphabet | Statement: [UP24, languageOfPrefix, English alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfPrefix Context triple: [UP24, languageOfPrefix, English alphabet]
-
A.
suffixLanguage
chosen
Indicates that one language is used as a suffix or ending element in the formation or representation of another language or linguistic expression.
-
B.
languagePreservedBy
Indicates that a language continues to exist, be maintained, or be kept from extinction through the efforts, practices, or protection of a specified agent or entity.
-
C.
languageAtTerminus
Indicates the language used or associated with the endpoint or terminus of something (such as a route, connection, or communication).
-
D.
languageCategory
Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
-
E.
languageName
Indicates the specific name assigned to a language in the relationship.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: April 29, 2026, 9:17 p.m.