Triple
T32123629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSRunLoop |
E820441
|
entity |
| Predicate | commonModeName |
P196252
|
FINISHED |
| Object | NSDefaultRunLoopMode |
—
|
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: NSDefaultRunLoopMode | Statement: [NSRunLoop, commonModeName, NSDefaultRunLoopMode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonModeName Context triple: [NSRunLoop, commonModeName, NSDefaultRunLoopMode]
-
A.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
B.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
C.
moreCommonPublicName
Indicates that one name is used more frequently or popularly in public contexts than another alternative name for the same entity.
-
D.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
-
E.
moreCommonFrom
Indicates that one entity occurs or appears more frequently originating from, or associated with, the source specified by the other entity than from alternative sources.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fe189f2ea48190b8c4718f1353970e |
completed | May 8, 2026, 5:08 p.m. |
Created at: May 1, 2026, 12:29 a.m.