Triple
T26916328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigenère table |
E677525
|
entity |
| Predicate | canBeAdaptedFor |
P160937
|
FINISHED |
| Object | non-English alphabets |
—
|
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: non-English alphabets | Statement: [Vigenère table, canBeAdaptedFor, non-English alphabets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAdaptedFor Context triple: [Vigenère table, canBeAdaptedFor, non-English alphabets]
-
A.
mayBeAdaptedTo
chosen
Indicates that something has the potential or suitability to be modified or adjusted for use in a different context, condition, or purpose.
-
B.
canBeAdaptedBy
Indicates that one entity is capable of being modified, adjusted, or tailored for use by another entity.
-
C.
adaptedTo
Indicates that one entity has been modified, adjusted, or evolved to function effectively within the conditions, requirements, or characteristics defined by another entity.
-
D.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter another entity.
-
E.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 27, 2026, 6:04 a.m.