Triple
T28616370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CreateSemaphore |
E724281
|
entity |
| Predicate | characterSetVariant |
P189430
|
FINISHED |
| Object | CreateSemaphoreA |
—
|
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: CreateSemaphoreA | Statement: [CreateSemaphore, characterSetVariant, CreateSemaphoreA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterSetVariant Context triple: [CreateSemaphore, characterSetVariant, CreateSemaphoreA]
-
A.
characterSetVariants
chosen
Indicates that one character set is a variant or alternative form of another character set.
-
B.
characterSetType
Indicates the type or category of character set associated with or used by an entity.
-
C.
characterSetOrigin
Indicates the source or defining system from which a particular character set is derived or specified.
-
D.
characterSetStorage
Indicates that a particular character set is used for storing data in a given context or system.
-
E.
featuresCharacterVariant
Indicates that one entity includes or presents an alternative or variant form of a character represented by 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_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 28, 2026, 4:32 a.m.