Triple
T29912108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVAudioSession |
E759694
|
entity |
| Predicate | singletonAccess |
P168247
|
FINISHED |
| Object | +sharedInstance |
—
|
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: +sharedInstance | Statement: [AVAudioSession, singletonAccess, +sharedInstance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singletonAccess Context triple: [AVAudioSession, singletonAccess, +sharedInstance]
-
A.
singleWith
Indicates that an entity is unmarried and not currently in a romantic relationship.
-
B.
singleBy
Indicates that an entity is not in a romantic relationship and is considered single according to a specified criterion or context.
-
C.
singleContext
Indicates that the entity or event occurs, is interpreted, or is valid within exactly one specific context, rather than across multiple contexts.
-
D.
singleType
Indicates that an entity belongs to exactly one specific type or category, with no additional types assigned.
-
E.
singleFrom
Indicates that one entity is derived as a single, distinct item from another source or collection.
- F. None of above. chosen
Provenance (4 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6775b7e54819083176ce918b32eec |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:10 p.m.