Triple
T28616144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LoadLibrary |
E724276
|
entity |
| Predicate | characterEncodingVariant |
P174376
|
FINISHED |
| Object | LoadLibraryA is ANSI version |
—
|
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: LoadLibraryA is ANSI version | Statement: [LoadLibrary, characterEncodingVariant, LoadLibraryA is ANSI version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterEncodingVariant Context triple: [LoadLibrary, characterEncodingVariant, LoadLibraryA is ANSI version]
-
A.
hasUnicodeVariant
chosen
Indicates that one entity has an alternative representation or equivalent form in Unicode corresponding to the other entity.
-
B.
localEncoding
Indicates that an entity is represented or stored using a specific encoding scheme that is defined or applied locally within a particular context or system.
-
C.
encodingIndependence
Indicates that a relationship or property holds regardless of the specific encoding or representation used for the involved entities.
-
D.
usesCharacterSet
Indicates that one entity employs or relies on a specific character set defined by another entity for encoding or representing text.
-
E.
encodingIs
Indicates that one entity serves as the specific encoding or coded representation of another entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 28, 2026, 4:32 a.m.