Triple
T5634092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Default Unicode Collation Element Table |
E147902
|
entity |
| Predicate | canBeCustomizedBy |
P33710
|
FINISHED |
| Object | locale-specific tailoring |
—
|
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: locale-specific tailoring | Statement: [Default Unicode Collation Element Table, canBeCustomizedBy, locale-specific tailoring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeCustomizedBy Context triple: [Default Unicode Collation Element Table, canBeCustomizedBy, locale-specific tailoring]
-
A.
customizableBy
chosen
Indicates that one entity can be modified, configured, or tailored in some way by another entity.
-
B.
canBeAdaptedBy
Indicates that one entity is capable of being modified, adjusted, or tailored for use by another entity.
-
C.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
D.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
E.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0226118548190877793dadf6cacba |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.